BMC/Intel-BMC/linux.git/Documentation/dmaengine/provider.txt, branch dev-4.4

Documentation: dmaengine: Add DMA_CTRL_REUSE documentation

2015-08-17T08:16:22+00:00

Signed-off-by: Vinod Koul Acked-by:Robert Jarzmik

Documentation: dmaengine: fix the DMA_CTRL_ACK documentation

2015-08-17T08:16:22+00:00

As discussed recently the meaning of DMA_CTRL_ACK is that a desc cannot be reused by provider until the client acknowledges receipt, i.e. has has a chance to establish any dependency chains. So update documentation Signed-off-by: Vinod Koul Acked-by:Robert Jarzmik

Documentation: dmaengine: document DMA_CTRL_ACK

2015-06-17T16:46:15+00:00

Add documentation about acking the transfers, and their reusability. Signed-off-by: Robert Jarzmik Acked-by: Maxime Ripard Signed-off-by: Vinod Koul

Documentation: dmaengine: clarify dma_slave_config expectations

2014-12-22T07:04:22+00:00

dma_slave_config is expected to be set for slave operations Only, not for memcpy ones Signed-off-by: Vinod Koul

Documentation: dmaengine: Update the documentation

2014-12-22T07:04:22+00:00

Now that we have splitted device_control and removed device_slave_caps in favor of a few dma_device variables, update the documentation accordingly. Signed-off-by: Maxime Ripard Signed-off-by: Vinod Koul

Documentation: dmaengine: Add a documentation for the dma controller API

2014-11-06T05:45:58+00:00

The dmaengine is neither trivial nor properly documented at the moment, which means a lot of trial and error development, which is not that good for such a central piece of the system. Attempt at making such a documentation. Signed-off-by: Maxime Ripard [fixed some minor typos] Signed-off-by: Vinod Koul