Lines Matching +full:wait +full:- +full:queue

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
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
40    .. code-block:: c
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
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:
243     - DMA_DEV_TO_MEM:
263    added, it must be placed on the DMA engine drivers pending queue.
267    .. code-block:: c
275    it to the pending queue. For this, see step 5, dma_async_issue_pending.
284 5. Issue pending DMA requests and wait for callback notification
286    The transactions in the pending queue can be activated by calling the
288    queue is started and subsequent ones queued up.
290    On completion of each DMA operation, the next in queue is started and
296    .. code-block:: c
301 ------------
305    .. code-block:: c
317    dmaengine_terminate_async() might not wait until the DMA has been fully
324    dmaengine_terminate_sync() will wait for the transfer and any running
332    .. code-block:: c
340    .. code-block:: c
349    .. code-block:: c
371    .. code-block:: c
379    wait for the transfer and any running complete callbacks to finish before it