Lines Matching refs:transfer

7      A driver submitting a transfer and issuing it should be granted the transfer
9      This implies that the queuing doesn't wait for the previous transfer end,
11      triggered by the end of the transfer.
12      A transfer which is submitted and issued on a phy doesn't wait for a phy to
15      a new transfer.
18      Any issued transfer with DMA_PREP_INTERRUPT should trigger a callback call.
25      multimedia case, such as video capture, if a transfer is submitted and then
26      a check of the DMA channel reports a "stopped channel", the transfer should
42      assigned on the fly when the transfer is issued.
44   b) Transfer anatomy for a scatter-gather transfer
55         a trace that this transfer is done. The "well known" is unique per
57         is the last finished transfer at that point in time.
59       - linker: has ddadr= desc-sg[0] of next transfer, dcmd=0
81      dma_async_issue_pending() is to be used to ensure the transfer is actually started.
88          such a transfer tx_submit() will be queued on the submitted queue, and
92      Each time a transfer is completed on a channel, an interrupt might be
94      descriptor of a transfer, the "status updater", will write the latest
95      transfer being completed into the physical channel's completion mark.
99      any lock to find out what is the latest completed transfer in a running
103      When a transfer flagged as "DMA_PREP_INTERRUPT" is finished, the dma irq
108       - calling all the transfer callbacks of finished transfers, based on
109         that mark, and each transfer flags.
110      If a transfer is completed while this handling is done, a dma irq will