diff options
| author | Kendra Moore <kendra.j.moore3443@gmail.com> | 2025-04-20 21:02:05 -0400 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2025-05-07 01:02:57 -0600 |
| commit | fea017a99ba5e28b23f8249c04b2f475e4ed1fb3 (patch) | |
| tree | d0da1030a2a02d09a4f369cf4c3e6db38c06ae52 | |
| parent | 422f5b78bfb16e6e207d5f280ee75517ca365458 (diff) | |
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 <kendra.j.moore3443@gmail.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Message-ID: <20250421010205.84719-1-kendra.j.moore3443@gmail.com>
| -rw-r--r-- | Documentation/driver-api/dmaengine/provider.rst | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/Documentation/driver-api/dmaengine/provider.rst b/Documentation/driver-api/dmaengine/provider.rst index 3085f8b460fa..8f0910668ca3 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 |