summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/dma/nbpfaxi.txt (follow)
Commit message (Collapse)AuthorAgeFilesLines
* dt-bindings: dmaengine: nbpfaxi: Rename bindings documentation fileSimon Horman2019-08-201-69/+0
| | | | | | | | | | | | | Rename the device tree bindings for renesas "Type-AXI" NBPFAXI* DMA controllers from nbpfaxi.txt to renesas,nbpfaxi.txt. This is part of an ongoing effort to name bindings documentation files for Renesas IP blocks consistently, in line with the compat strings they document. Signed-off-by: Simon Horman <horms+renesas@verge.net.au> Link: https://lore.kernel.org/r/20190819135244.18183-1-horms+renesas@verge.net.au Signed-off-by: Vinod Koul <vkoul@kernel.org>
* dmaengine: nbpfaxi: add optional max-burst property for memory reads/writesNiklas Cassel2016-11-141-0/+8
| | | | | | | | | | | | | | | | | | Due to a hardware bug, reading memory (from the Accelerator Coherency Port) with a burst size equal to the maximum burst size allowed by the DMA hardware's buffer size will cause a hardware hang on the ARTPEC-6 SoC, where the only solution is a manual power cycle. On ARTPEC-6, this hardware bug does not trigger when writing memory (to the Accelerator Coherency Port) with a burst size equal to the maximum burst size allowed by the DMA hardware's buffer size. To avoid this hardware hang, introduce a new optional max-burst property for memory reads. For completeness, also introduce a max-burst property for memory writes. Signed-off-by: Niklas Cassel <niklas.cassel@axis.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
* dmaengine: add device tree binding documentation for the nbpfaxi driverGuennadi Liakhovetski2014-08-041-0/+61
The nbpfaxi dmaengine driver doesn't define any new bindings, it only uses standard dmaengine bindings and defines 3 flags for the 3rd parameter of the "dmas" property. Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com> Acked-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Vinod Koul <vinod.koul@intel.com>