summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorGeert Uytterhoeven <geert+renesas@glider.be>2014-08-20 09:18:44 -0400
committerVinod Koul <vinod.koul@intel.com>2014-08-28 03:07:55 -0400
commit58d06e989e1321b43c1e42bdf3846113e9e16ecd (patch)
treeea164e145ae2422da264db639a8dab3a51128f41 /Documentation
parent29a4bb1431035560b4be3fc5917c5ab8b8141204 (diff)
dmaengine: Update documentation for inline wrapper
Commit 16052827d98fbc13c31ebad560af4bd53e2b4dd5 ("dmaengine/dma_slave: introduce inline wrappers") introduced some wrappers, but there is still a reference to the old function. Update the documentation to use the wrapper, and add a missing "()" to a function name. Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/dmaengine.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/dmaengine.txt b/Documentation/dmaengine.txt
index 573e28ce9751..11fb87ff6cd0 100644
--- a/Documentation/dmaengine.txt
+++ b/Documentation/dmaengine.txt
@@ -98,7 +98,7 @@ The slave DMA usage consists of following steps:
98 unsigned long flags); 98 unsigned long flags);
99 99
100 The peripheral driver is expected to have mapped the scatterlist for 100 The peripheral driver is expected to have mapped the scatterlist for
101 the DMA operation prior to calling device_prep_slave_sg, and must 101 the DMA operation prior to calling dmaengine_prep_slave_sg(), and must
102 keep the scatterlist mapped until the DMA operation has completed. 102 keep the scatterlist mapped until the DMA operation has completed.
103 The scatterlist must be mapped using the DMA struct device. 103 The scatterlist must be mapped using the DMA struct device.
104 If a mapping needs to be synchronized later, dma_sync_*_for_*() must be 104 If a mapping needs to be synchronized later, dma_sync_*_for_*() must be
@@ -195,5 +195,5 @@ Further APIs:
195 Note: 195 Note:
196 Not all DMA engine drivers can return reliable information for 196 Not all DMA engine drivers can return reliable information for
197 a running DMA channel. It is recommended that DMA engine users 197 a running DMA channel. It is recommended that DMA engine users
198 pause or stop (via dmaengine_terminate_all) the channel before 198 pause or stop (via dmaengine_terminate_all()) the channel before
199 using this API. 199 using this API.