Lines Matching +full:free +full:- +full:running

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   - dma_cyclic: Perform a cyclic DMA operation from/to a peripheral till the
86   - interleaved_dma: This is common to Slave as well as M2M clients. For slave
93   A non-NULL return of this transfer API represents a "descriptor" for
98   .. code-block:: c
121   .. code-block:: c
167   .. code-block:: c
186   .. code-block:: c
196   .. code-block:: c
205     - DMA_MEM_TO_DEV / DEV_MEM_TO_MEM:
213     - DMA_DEV_TO_MEM:
224     - DMA_MEM_TO_DEV / DEV_MEM_TO_MEM:
234     - DMA_DEV_TO_MEM:
258    .. code-block:: c
287    .. code-block:: c
292 ------------
296    .. code-block:: c
309    stopped or until any running complete callbacks have finished. But it is
312    is safe to free the memory accessed by the DMA transfer or free resources
315    dmaengine_terminate_sync() will wait for the transfer and any running
323    .. code-block:: c
331    .. code-block:: c
340    .. code-block:: c
356       a running DMA channel. It is recommended that DMA engine users
362    .. code-block:: c
370    wait for the transfer and any running complete callbacks to finish before it
374    must be called before it is safe to free memory accessed by previously
375    submitted descriptors or to free any resources accessed within the complete