Lines Matching refs:transfers

11 They have a given number of channels to use for the DMA transfers, and
41 really efficient, you'll get several bigger transfers. This is done
44 transfer into smaller sub-transfers.
46 Our theoretical DMA controller would then only be able to do transfers
48 transfers we usually have are not, and want to copy data from
52 DMAEngine, at least for mem2dev transfers, require support for
80 memory-to-device (mem2dev) kind of transfers. Most devices often
81 support other kind of transfers or memory operations that dmaengine
91 Over time, the need for memory to device transfers arose, and
125   (i.e. excluding mem2mem transfers)
196   - The devices only supports slave transfers, and as such isn't
197     available for async transfers.
208   - The device can handle device to memory transfers, including
209     scatter-gather transfers.
221   - The device can handle cyclic transfers.
226   - It's usually used for audio transfers, where you want to operate
233   - These transfers can transfer data from a non-contiguous buffer
238   - It's usually used for 2d content transfers, in which case you
353     currently queued transfers, but only on subsequent ones
384   - Aborts all the pending and ongoing transfers on the channel
386   - For aborted transfers the complete callback should not be called
420   ignored in the slave transfers case.
454   ``dma_map_sg()`` and ``dma_unmap_sg()`` in between 2 transfers,