Lines Matching refs:handler

27 - Each URB has a completion handler, which is called after the action
29   context-pointer for passing information to the completion handler.
109 the desired transfer length, the completion  handler, and its context. 
158 returns; you must still wait for the completion handler to be called.
165 until after the URB has been returned and the completion handler
167 that if the completion handler or anyone else tries to resubmit it
172 time, and the completion handler may free the URB.  If this happens
179 completion handler, the handler must not take any lock that is held
191 by the completion handler.
194 1.7. What about the completion handler?
196 The handler is of the following type:
201 handler, you should have a look at urb->status to detect any USB errors.
203 information to the completion handler.
259 restarted when they complete.  They end when the completion handler is
261 your completion handler must resubmit it.