Commit 1f854536 authored by Paul Kocialkowski's avatar Paul Kocialkowski Committed by Vinod Koul

dmaengine: Clarify cyclic transfer residue documentation

The current documentation for the residue reported in a cyclic transfer
case mentions that the reported residue should be relative to the current
period only. However the definition of DMA_RESIDUE_GRANULARITY_SEGMENT
specifies that the residue should be updated after each period for
a cyclic transfer, which is in direct contradiction.

Moreover the pcm_dmaengine common code uses the residue relative to
the whole cyclic buffer size, not one period.

Correct the residue-related documentation to reflect this.
Signed-off-by: default avatarPaul Kocialkowski <paul.kocialkowski@bootlin.com>
Link: https://lore.kernel.org/r/20220331134114.703782-1-paul.kocialkowski@bootlin.comSigned-off-by: default avatarVinod Koul <vkoul@kernel.org>
parent ec834f1c
...@@ -457,7 +457,7 @@ supported. ...@@ -457,7 +457,7 @@ supported.
- Should use dma_set_residue to report it - Should use dma_set_residue to report it
- In the case of a cyclic transfer, it should only take into - In the case of a cyclic transfer, it should only take into
account the current period. account the total size of the cyclic buffer.
- Should return DMA_OUT_OF_ORDER if the device does not support in order - Should return DMA_OUT_OF_ORDER if the device does not support in order
completion and is completing the operation out of order. completion and is completing the operation out of order.
......
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