From: Kendra Moore Date: Mon, 21 Apr 2025 01:02:05 +0000 (-0400) Subject: docs: dmaengine: add explanation for DMA_ASYNC_TX capability X-Git-Tag: v6.16-rc1~176^2~16 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fea017a99ba5e28b23f8249c04b2f475e4ed1fb3;p=thirdparty%2Fkernel%2Flinux.git docs: dmaengine: add explanation for DMA_ASYNC_TX capability This patch replaces the TODO for DMA_ASYNC_TX in the DMA engine provider documentation. The flag is automatically set by the DMA framework when a device supports key asynchronous memory-to-memory operations such as memcpy, memset, xor, pq, xor_val, and pq_val. It must not be set by drivers directly. Signed-off-by: Kendra Moore Signed-off-by: Jonathan Corbet Message-ID: <20250421010205.84719-1-kendra.j.moore3443@gmail.com> --- diff --git a/Documentation/driver-api/dmaengine/provider.rst b/Documentation/driver-api/dmaengine/provider.rst index 3085f8b460fa5..8f0910668ca31 100644 --- a/Documentation/driver-api/dmaengine/provider.rst +++ b/Documentation/driver-api/dmaengine/provider.rst @@ -217,10 +217,12 @@ Currently, the types available are: - DMA_ASYNC_TX - - Must not be set by the device, and will be set by the framework - if needed + - The device supports asynchronous memory-to-memory operations, + including memcpy, memset, xor, pq, xor_val, and pq_val. - - TODO: What is it about? + - This capability is automatically set by the DMA engine + framework and must not be configured manually by device + drivers. - DMA_SLAVE