driver-api/dmaengine/client.rst

23 - Get a descriptor for transaction
76 3. Get a descriptor for transaction
93   A non-NULL return of this transfer API represents a "descriptor" for
129   Once a descriptor has been obtained, the callback information can be
130   added and the descriptor must then be submitted. Some DMA engine
156   **Optional: per descriptor metadata**
163     attached to the descriptor.
178     after their transfer completion callback has run for the descriptor.
205       1. prepare the descriptor (dmaengine_prep_*)
208          descriptor
213       1. prepare the descriptor (dmaengine_prep_*)
215          descriptor
224       1. prepare the descriptor (dmaengine_prep_*)
234       1. prepare the descriptor (dmaengine_prep_*)
242      When DESC_METADATA_ENGINE mode is used the metadata area for the descriptor
247      client drivers must use either of the modes per descriptor.
251    Once the descriptor has been prepared and the callback information
268       After calling ``dmaengine_submit()`` the submitted transfer descriptor
271       descriptor.