Lines Matching refs:operation
17 3.4 When does the operation execute?
18 3.5 When does the operation complete?
35 that is written to the API can optimize for asynchronous operation and
51 operation will be offloaded when an engine is available and carried out
55 API automatically handles cases where the transition from one operation
57 3. dmaengine extensions to support multiple clients and operation types
69 async_<operation>(<op specific parameters>, struct async_submit_ctl *submit)
94 The return value is non-NULL and points to a 'descriptor' when the operation
109 3.4 When does the operation execute?
113 async_<operation> call. Offload engine drivers batch operations to
118 channels since the application has no knowledge of channel to operation
121 3.5 When does the operation complete?
125 of an operation.
128 it polls for the completion of the operation. It handles dependency
132 called in application context if the operation is carried out
134 async_<operation>, or when the application needs to submit a chain of
141 1. Calls to async_<operation> are not permitted in IRQ context. Other
150 Perform a xor->copy->xor operation where each operation depends on the
151 result from the previous operation::