Lines Matching full:callbacks

28 callbacks, the callback's rval argument contains the transport error status. A
98 Resources could not be allocated to process callbacks
99 asynchronously. Callbacks receiving this flag must not block, since those
100 callbacks are executing in a context which holds resources shared by the rest
101 of the system. Note that exception callbacks with USB_CB_ASYNC_REQ_FAILED set
103 callbacks may be already queued when an exception hits that the USBA is unable
142 driver notification. There are three kinds of callbacks: Normal completion
153 Each pipe is associated with a pool of threads that are used to run callbacks
154 associated with requests on that pipe.  All transfer completion callbacks for a
158 Pipes taking requests with callbacks which can block must have their pipe
162 Similarly, problems will ensue when callbacks overlap and there are not enough
163 threads to handle the number of overlapping callbacks.
167 threads to allocate for asynchronous processing of request callbacks on a pipe.
172 Transfer completion callbacks (normal completion and exception):
175 Most transfer completion callbacks are allowed to block, but only under certain
183 callbacks, plus those with USB_CB_ASYNC_REQ_FAILED set, execute in  interrupt
197 on the same pipe. The command could wait for all callbacks to complete,
206 Avoid callbacks that block for synchronous completion of commands done on
221 because all callbacks are done by a single thread.)
226 Note that if a callback blocks, other callbacks awaiting processing can
240 All request-callbacks take as arguments a usb_pipe_handle_t and a pointer to
251 Such callbacks can retrieve saved state or other information from the private
274 .SS "COMMAND COMPLETION CALLBACKS"
298 As with transfer completion callbacks, command completion callbacks take a
300 private area. Also, command completion callbacks are provided with an
311 for transfer completion callbacks, callback flags return additional information