Lines Matching refs:transfer

9 A driver submitting a transfer and issuing it should be granted the transfer
11 This implies that the queuing doesn't wait for the previous transfer end,
13 triggered by the end of the transfer.
14 A transfer which is submitted and issued on a phy doesn't wait for a phy to
17 a new transfer.
20 Any issued transfer with DMA_PREP_INTERRUPT should trigger a callback call.
27 multimedia case, such as video capture, if a transfer is submitted and then
28 a check of the DMA channel reports a "stopped channel", the transfer should
44 assigned on the fly when the transfer is issued.
46 b) Transfer anatomy for a scatter-gather transfer
62       a trace that this transfer is done. The "well known" is unique per
64       is the last finished transfer at that point in time.
68     - linker: has ddadr= desc-sg[0] of next transfer, dcmd=0
96 dma_async_issue_pending() is to be used to ensure the transfer is actually started.
106   such a transfer tx_submit() will be queued on the submitted queue, and
110 Each time a transfer is completed on a channel, an interrupt might be
112 descriptor of a transfer, the "status updater", will write the latest
113 transfer being completed into the physical channel's completion mark.
117 any lock to find out what is the latest completed transfer in a running
121 When a transfer flagged as "DMA_PREP_INTERRUPT" is finished, the dma irq
129 - calling all the transfer callbacks of finished transfers, based on
130   that mark, and each transfer flags.
132 If a transfer is completed while this handling is done, a dma irq will