Skip to contentSkip to conversation

docs: dmaengine: add explanation for DMA_ASYNC_TX capability

PATCH Applied kendrajmoore 2 participants 2 messages Apr 21, 2025 – May 6, 2025

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 docs: dmaengine: add explanation for DMA_ASYNC_TX capability

From: Kendra Moore <[email protected]>

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.

---
 Documentation/driver-api/dmaengine/provider.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
Documentation/driver-api/dmaengine/provider.rst +5 -3
index 3085f8b460fa..aac2a18bd453 100644
@@ -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
 
Signature · 1 line
2.39.5
maintainer Applied
#1 lore raw
Quoted 7 lines · kendrajmoore

From: Kendra Moore <[email protected]>

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.

Quoted 6 lines

It must not be set by drivers directly.

---
 Documentation/driver-api/dmaengine/provider.rst | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

Applied, thanks.