archives/linux
1
0
Fork 0
mirror of https://github.com/torvalds/linux.git synced 2026-03-14 00:56:20 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: dmaengine: add explanation for DMA_ASYNC_TX capability

Browse source 
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>
This commit is contained in:
Kendra Moore 2025-04-20 21:02:05 -04:00 • committed by Jonathan Corbet
parent 422f5b78bf
commit fea017a99b
1 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
Documentation/driver-api/dmaengine/provider.rst
View file

@ -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