-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'dmaengine-5.1-rc1' of git://git.infradead.org/users/vkoul/…
…slave-dma Pull dmaengine updates from Vinod Koul: - dmatest updates for modularizing common struct and code - remove SG support for VDMA xilinx IP and updates to driver - Update to dw driver to support Intel iDMA controllers multi-block support - tegra updates for proper reporting of residue - Add Snow Ridge ioatdma device id and support for IOATDMA v3.4 - struct_size() usage and useless LIST_HEAD cleanups in subsystem. - qDMA controller driver for Layerscape SoCs - stm32-dma PM Runtime support - And usual updates to imx-sdma, sprd, Documentation, fsl-edma, bcm2835, qcom_hidma etc * tag 'dmaengine-5.1-rc1' of git://git.infradead.org/users/vkoul/slave-dma: (81 commits) dmaengine: imx-sdma: fix consistent dma test failures dmaengine: imx-sdma: add a test for imx8mq multi sdma devices dmaengine: imx-sdma: add clock ratio 1:1 check dmaengine: dmatest: move test data alloc & free into functions dmaengine: dmatest: add short-hand `buf_size` var in dmatest_func() dmaengine: dmatest: wrap src & dst data into a struct dmaengine: ioatdma: support latency tolerance report (LTR) for v3.4 dmaengine: ioatdma: add descriptor pre-fetch support for v3.4 dmaengine: ioatdma: disable DCA enabling on IOATDMA v3.4 dmaengine: ioatdma: Add Snow Ridge ioatdma device id dmaengine: sprd: Change channel id to slave id for DMA cell specifier dt-bindings: dmaengine: sprd: Change channel id to slave id for DMA cell specifier dmaengine: mv_xor: Use correct device for DMA API Documentation :dmaengine: clarify DMA desc. pointer after submission Documentation: dmaengine: fix dmatest.rst warning dmaengine: k3dma: Add support for dma-channel-mask dmaengine: k3dma: Delete axi_config dmaengine: k3dma: Upgrade k3dma driver to support hisi_asp_dma hardware Documentation: bindings: dma: Add binding for dma-channel-mask Documentation: bindings: k3dma: Extend the k3dma driver binding to support hisi-asp ...
- Loading branch information
Showing
61 changed files
with
2,592 additions
and
654 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
NXP Layerscape SoC qDMA Controller | ||
================================== | ||
|
||
This device follows the generic DMA bindings defined in dma/dma.txt. | ||
|
||
Required properties: | ||
|
||
- compatible: Must be one of | ||
"fsl,ls1021a-qdma": for LS1021A Board | ||
"fsl,ls1043a-qdma": for ls1043A Board | ||
"fsl,ls1046a-qdma": for ls1046A Board | ||
- reg: Should contain the register's base address and length. | ||
- interrupts: Should contain a reference to the interrupt used by this | ||
device. | ||
- interrupt-names: Should contain interrupt names: | ||
"qdma-queue0": the block0 interrupt | ||
"qdma-queue1": the block1 interrupt | ||
"qdma-queue2": the block2 interrupt | ||
"qdma-queue3": the block3 interrupt | ||
"qdma-error": the error interrupt | ||
- fsl,dma-queues: Should contain number of queues supported. | ||
- dma-channels: Number of DMA channels supported | ||
- block-number: the virtual block number | ||
- block-offset: the offset of different virtual block | ||
- status-sizes: status queue size of per virtual block | ||
- queue-sizes: command queue size of per virtual block, the size number | ||
based on queues | ||
|
||
Optional properties: | ||
|
||
- dma-channels: Number of DMA channels supported by the controller. | ||
- big-endian: If present registers and hardware scatter/gather descriptors | ||
of the qDMA are implemented in big endian mode, otherwise in little | ||
mode. | ||
|
||
Examples: | ||
|
||
qdma: dma-controller@8390000 { | ||
compatible = "fsl,ls1021a-qdma"; | ||
reg = <0x0 0x8388000 0x0 0x1000>, /* Controller regs */ | ||
<0x0 0x8389000 0x0 0x1000>, /* Status regs */ | ||
<0x0 0x838a000 0x0 0x2000>; /* Block regs */ | ||
interrupts = <GIC_SPI 185 IRQ_TYPE_LEVEL_HIGH>, | ||
<GIC_SPI 76 IRQ_TYPE_LEVEL_HIGH>, | ||
<GIC_SPI 77 IRQ_TYPE_LEVEL_HIGH>; | ||
interrupt-names = "qdma-error", | ||
"qdma-queue0", "qdma-queue1"; | ||
dma-channels = <8>; | ||
block-number = <2>; | ||
block-offset = <0x1000>; | ||
fsl,dma-queues = <2>; | ||
status-sizes = <64>; | ||
queue-sizes = <64 64>; | ||
big-endian; | ||
}; | ||
|
||
DMA clients must use the format described in dma/dma.txt file. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.