Commit 70c9b8bd authored by Geert Uytterhoeven's avatar Geert Uytterhoeven Committed by Vinod Koul

dmaengine: Clarify device parameter for dma_sync_*_for_*()

Signed-off-by: default avatarGeert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: default avatarVinod Koul <vinod.koul@intel.com>
parent 211bfef7
...@@ -100,8 +100,10 @@ The slave DMA usage consists of following steps: ...@@ -100,8 +100,10 @@ The slave DMA usage consists of following steps:
The peripheral driver is expected to have mapped the scatterlist for The peripheral driver is expected to have mapped the scatterlist for
the DMA operation prior to calling device_prep_slave_sg, and must the DMA operation prior to calling device_prep_slave_sg, and must
keep the scatterlist mapped until the DMA operation has completed. keep the scatterlist mapped until the DMA operation has completed.
The scatterlist must be mapped using the DMA struct device. So, The scatterlist must be mapped using the DMA struct device.
normal setup should look like this: If a mapping needs to be synchronized later, dma_sync_*_for_*() must be
called using the DMA struct device, too.
So, normal setup should look like this:
nr_sg = dma_map_sg(chan->device->dev, sgl, sg_len); nr_sg = dma_map_sg(chan->device->dev, sgl, sg_len);
if (nr_sg == 0) if (nr_sg == 0)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment