Lines Matching +full:engine +full:- +full:specific

2 DMA Engine API Guide
7 .. note:: For DMA Engine usage in async_tx please see:
8           ``Documentation/crypto/async-tx-api.rst``
11 Below is a guide to device driver writers on how to use the Slave-DMA API of the
12 DMA Engine. This is applicable only for slave DMA usage only.
19 - Allocate a DMA slave channel
21 - Set slave and controller specific parameters
23 - Get a descriptor for transaction
25 - Submit the transaction
27 - Issue pending requests and wait for callback notification
35    controller only and even in some cases a specific channel is desired.
40    .. code-block:: c
51 2. Set slave and controller specific parameters
53    Next step is always to pass some specific information to the DMA
61    specific structure. That gives flexibility to client to pass more
66    .. code-block:: c
79   DMA-engine are:
81   - slave_sg: DMA a list of scatter gather buffers from/to a peripheral
83   - peripheral_dma_vec: DMA an array of scatter gather buffers from/to a
87   - dma_cyclic: Perform a cyclic DMA operation from/to a peripheral till the
90   - interleaved_dma: This is common to Slave as well as M2M clients. For slave
97   A non-NULL return of this transfer API represents a "descriptor" for
102   .. code-block:: c
130   .. code-block:: c
141   added and the descriptor must then be submitted. Some DMA engine
160      Therefore, it is important that DMA engine drivers drop any
176   .. code-block:: c
195   .. code-block:: c
205   .. code-block:: c
214     - DMA_MEM_TO_DEV / DEV_MEM_TO_MEM:
222     - DMA_DEV_TO_MEM:
233     - DMA_MEM_TO_DEV / DEV_MEM_TO_MEM:
237          engine's metadata area
239       4. use dmaengine_desc_set_metadata_len()  to tell the DMA engine the
243     - DMA_DEV_TO_MEM:
248          the pointer to the engine's metadata area
263    added, it must be placed on the DMA engine drivers pending queue.
267    .. code-block:: c
271    This returns a cookie can be used to check the progress of DMA engine
272    activity via other DMA engine calls not covered in this document.
280       (``struct dma_async_tx_descriptor``) belongs to the DMA engine.
296    .. code-block:: c
301 ------------
305    .. code-block:: c
332    .. code-block:: c
340    .. code-block:: c
349    .. code-block:: c
360    completion of a specific DMA transaction.
364       Not all DMA engine drivers can return reliable information for
365       a running DMA channel. It is recommended that DMA engine users
371    .. code-block:: c