Lines Matching full:callback

27 - Issue pending requests and wait for callback notification
140   Once a descriptor has been obtained, the callback information can be
148      Although the async_tx API specifies that completion callback
153      for submission prior to callback function being invoked, so
157      For cyclic DMA, a callback function may wish to terminate the
161      locks before calling the callback function which may cause a
189     after their transfer completion callback has run for the descriptor.
190     If no completion callback has been defined for the transfer, then the
193     completed, then the client must use completion callback.
255      point when the completion callback returns if used).
262    Once the descriptor has been prepared and the callback information
284 5. Issue pending DMA requests and wait for callback notification
292    completion callback routine for notification, if set.
313    No callback functions will be called for any incomplete transfers.
320    within a complete callback. dmaengine_synchronize() must be called before it
322    accessed from within the complete callback.
326    called from atomic context or from within a complete callback.
385    callback of previously submitted descriptors.