diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2014-01-29 23:27:23 -0500 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-01-29 23:27:23 -0500 |
| commit | ca2a650f3dfdc30d71d21bcbb04d2d057779f3f9 (patch) | |
| tree | 12e5f7f4dea5ba17cc82f2c633bbe9dbf725fb11 /Documentation/devicetree | |
| parent | e9e352e9100b98aed1a5fb9e33355c29fb07d5b1 (diff) | |
| parent | 15cec530e4bc7bed3f51cde8404f96fd28a8c7c5 (diff) | |
Merge branch 'for-linus' of git://git.infradead.org/users/vkoul/slave-dma
Pull slave-dma updates from Vinod Koul:
- new driver for BCM2835 used in R-pi
- new driver for MOXA ART
- dma_get_any_slave_channel API for DT based systems
- minor fixes and updates spread acrooss driver
[ The fsl-ssi dual fifo mode support addition clashed badly with the
other changes to fsl-ssi that came in through the sound merge. I did
a very rough cut at fixing up the conflict, but Nicolin Chen (author
of both sides) will need to verify and check things ]
* 'for-linus' of git://git.infradead.org/users/vkoul/slave-dma: (36 commits)
dmaengine: mmp_pdma: fix mismerge
dma: pl08x: Export pl08x_filter_id
acpi-dma: align documentation with kernel-doc format
dma: fix vchan_cookie_complete() debug print
DMA: dmatest: extend the "device" module parameter to 32 characters
drivers/dma: fix error return code
dma: omap: Set debug level to debugging messages
dmaengine: fix kernel-doc style typos for few comments
dma: tegra: add support for Tegra148/124
dma: dw: use %pad instead of casting dma_addr_t
dma: dw: join split up messages
dma: dw: fix style of multiline comment
dmaengine: k3dma: fix sparse warnings
dma: pl330: Use dma_get_slave_channel() in the of xlate callback
dma: pl330: Differentiate between submitted and issued descriptors
dmaengine: sirf: Add device_slave_caps interface
DMA: Freescale: change BWC from 256 bytes to 1024 bytes
dmaengine: Add MOXA ART DMA engine driver
dmaengine: Add DMA_PRIVATE to BCM2835 driver
dma: imx-sdma: Assign a default script number for ROM firmware cases
...
Diffstat (limited to 'Documentation/devicetree')
3 files changed, 103 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/dma/bcm2835-dma.txt b/Documentation/devicetree/bindings/dma/bcm2835-dma.txt new file mode 100644 index 000000000000..1396078d15ac --- /dev/null +++ b/Documentation/devicetree/bindings/dma/bcm2835-dma.txt | |||
| @@ -0,0 +1,57 @@ | |||
| 1 | * BCM2835 DMA controller | ||
| 2 | |||
| 3 | The BCM2835 DMA controller has 16 channels in total. | ||
| 4 | Only the lower 13 channels have an associated IRQ. | ||
| 5 | Some arbitrary channels are used by the firmware | ||
| 6 | (1,3,6,7 in the current firmware version). | ||
| 7 | The channels 0,2 and 3 have special functionality | ||
| 8 | and should not be used by the driver. | ||
| 9 | |||
| 10 | Required properties: | ||
| 11 | - compatible: Should be "brcm,bcm2835-dma". | ||
| 12 | - reg: Should contain DMA registers location and length. | ||
| 13 | - interrupts: Should contain the DMA interrupts associated | ||
| 14 | to the DMA channels in ascending order. | ||
| 15 | - #dma-cells: Must be <1>, the cell in the dmas property of the | ||
| 16 | client device represents the DREQ number. | ||
| 17 | - brcm,dma-channel-mask: Bit mask representing the channels | ||
| 18 | not used by the firmware in ascending order, | ||
| 19 | i.e. first channel corresponds to LSB. | ||
| 20 | |||
| 21 | Example: | ||
| 22 | |||
| 23 | dma: dma@7e007000 { | ||
| 24 | compatible = "brcm,bcm2835-dma"; | ||
| 25 | reg = <0x7e007000 0xf00>; | ||
| 26 | interrupts = <1 16>, | ||
| 27 | <1 17>, | ||
| 28 | <1 18>, | ||
| 29 | <1 19>, | ||
| 30 | <1 20>, | ||
| 31 | <1 21>, | ||
| 32 | <1 22>, | ||
| 33 | <1 23>, | ||
| 34 | <1 24>, | ||
| 35 | <1 25>, | ||
| 36 | <1 26>, | ||
| 37 | <1 27>, | ||
| 38 | <1 28>; | ||
| 39 | |||
| 40 | #dma-cells = <1>; | ||
| 41 | brcm,dma-channel-mask = <0x7f35>; | ||
| 42 | }; | ||
| 43 | |||
| 44 | DMA clients connected to the BCM2835 DMA controller must use the format | ||
| 45 | described in the dma.txt file, using a two-cell specifier for each channel. | ||
| 46 | |||
| 47 | Example: | ||
| 48 | |||
| 49 | bcm2835_i2s: i2s@7e203000 { | ||
| 50 | compatible = "brcm,bcm2835-i2s"; | ||
| 51 | reg = < 0x7e203000 0x20>, | ||
| 52 | < 0x7e101098 0x02>; | ||
| 53 | |||
| 54 | dmas = <&dma 2>, | ||
| 55 | <&dma 3>; | ||
| 56 | dma-names = "tx", "rx"; | ||
| 57 | }; | ||
diff --git a/Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt b/Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt index 4fa814d38321..68b83ecc3850 100644 --- a/Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt +++ b/Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt | |||
| @@ -42,6 +42,7 @@ The full ID of peripheral types can be found below. | |||
| 42 | 19 IPU Memory | 42 | 19 IPU Memory |
| 43 | 20 ASRC | 43 | 20 ASRC |
| 44 | 21 ESAI | 44 | 21 ESAI |
| 45 | 22 SSI Dual FIFO (needs firmware ver >= 2) | ||
| 45 | 46 | ||
| 46 | The third cell specifies the transfer priority as below. | 47 | The third cell specifies the transfer priority as below. |
| 47 | 48 | ||
diff --git a/Documentation/devicetree/bindings/dma/moxa,moxart-dma.txt b/Documentation/devicetree/bindings/dma/moxa,moxart-dma.txt new file mode 100644 index 000000000000..8a9f3559335b --- /dev/null +++ b/Documentation/devicetree/bindings/dma/moxa,moxart-dma.txt | |||
| @@ -0,0 +1,45 @@ | |||
| 1 | MOXA ART DMA Controller | ||
| 2 | |||
| 3 | See dma.txt first | ||
| 4 | |||
| 5 | Required properties: | ||
| 6 | |||
| 7 | - compatible : Must be "moxa,moxart-dma" | ||
| 8 | - reg : Should contain registers location and length | ||
| 9 | - interrupts : Should contain an interrupt-specifier for the sole | ||
| 10 | interrupt generated by the device | ||
| 11 | - #dma-cells : Should be 1, a single cell holding a line request number | ||
| 12 | |||
| 13 | Example: | ||
| 14 | |||
| 15 | dma: dma@90500000 { | ||
| 16 | compatible = "moxa,moxart-dma"; | ||
| 17 | reg = <0x90500080 0x40>; | ||
| 18 | interrupts = <24 0>; | ||
| 19 | #dma-cells = <1>; | ||
| 20 | }; | ||
| 21 | |||
| 22 | |||
| 23 | Clients: | ||
| 24 | |||
| 25 | DMA clients connected to the MOXA ART DMA controller must use the format | ||
| 26 | described in the dma.txt file, using a two-cell specifier for each channel: | ||
| 27 | a phandle plus one integer cells. | ||
| 28 | The two cells in order are: | ||
| 29 | |||
| 30 | 1. A phandle pointing to the DMA controller. | ||
| 31 | 2. Peripheral identifier for the hardware handshaking interface. | ||
| 32 | |||
| 33 | Example: | ||
| 34 | Use specific request line passing from dma | ||
| 35 | For example, MMC request line is 5 | ||
| 36 | |||
| 37 | sdhci: sdhci@98e00000 { | ||
| 38 | compatible = "moxa,moxart-sdhci"; | ||
| 39 | reg = <0x98e00000 0x5C>; | ||
| 40 | interrupts = <5 0>; | ||
| 41 | clocks = <&clk_apb>; | ||
| 42 | dmas = <&dma 5>, | ||
| 43 | <&dma 5>; | ||
| 44 | dma-names = "tx", "rx"; | ||
| 45 | }; | ||
