Lines Matching refs:can

13 Requests and channels are pretty much orthogonal. Channels can be used
34 is why most if not all of the DMA controllers can adjust this, using a
38 or destination, can group the reads or writes in memory into a buffer,
129     - This can be either:
187     - Even though a plain memcpy can look like a particular case of a
201     - The device can handle device to memory transfers, including
211     - The device can handle cyclic transfers.
219     - These transfers can transfer data from a non-contiguous buffer
220       to a non-contiguous buffer, opposed to DMA_SLAVE that can
254      - These functions can sleep.
262      - These functions can be called from an interrupt context
274      - This structure can be initialized using the function
290      - This function can be called in an interrupt context
300      - This function can be called in an interrupt context.
337     - Should be called at the end of an async TX transfer, and can be
351     - This can be acked by invoking async_tx_ack()
352     - If set, does not mean descriptor can be reused
355     - If set, the descriptor can be reused after being completed. It should
363       it can resubmit the transfer right after its completion.
364     - Descriptor can be freed in few ways
367 	- Explicitly invoking dmaengine_desc_free(), this can succeed only
387 order to have a shorter idle window (that we can't really avoid
394 		that can be queued to buffers before being flushed to