diff options
| author | Vinod Koul <vkoul@kernel.org> | 2026-10-09 11:37:44 +0200 |
|---|---|---|
| committer | Vinod Koul <vkoul@kernel.org> | 2026-10-11 21:32:55 +0100 |
| commit | fa89be96e845de705eed6edd01ecb79d46ee21c7 (patch) | |
| tree | c03190ab7430ad9fbc5c648692ccbd86a51bf54d /include/linux | |
| parent | 511afae96d89847f753fcab6b3a597f0281be9d5 (diff) | |
| download | linux-next-fa89be96e845de705eed6edd01ecb79d46ee21c7.tar.gz linux-next-fa89be96e845de705eed6edd01ecb79d46ee21c7.zip | |
docs: dmaengine: clarify ordering rules around cookie completion
Sashiko pointed in [1] about the cookie completion order. It is good to
Document that for ensuring that dma buffer is flushed and no stale data
is seeing by consumer, we need to make sure such action is taken before
drivers invoke dma cookie completion.
[1]: https://lore.kernel.org/r/20260917072507.5BDB61F000FF@smtp.kernel.org
Reviewed-by: Frank Li <Frank.Li@nxp.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Link: https://patch.msgid.link/20261009093745.539924-1-vkoul@kernel.org
Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions
