Cross Reference: /external/chromium_org/third

Lines Matching defs:libusb_handle_events
503  * This gives rise to the libusb_handle_events() function which your
507  * There are 2 different approaches to dealing with libusb_handle_events:
509  * -# Repeatedly call libusb_handle_events() in blocking mode from a dedicated
536         libusb_handle_events(ctx);
543  * event_thread_run variable to 0, and after that libusb_handle_events() needs
545  * libusb_handle_events() will not return.
559     libusb_close(handle); // This wakes up libusb_handle_events()
575     libusb_hotplug_deregister_callback(ctx, hotplug_cb_handle); // This wakes up libusb_handle_events()
602  * libusb_handle_events().
631 	libusb_handle_events(ctx);
637  * sets of file descriptors or handling timeouts. libusb_handle_events() will
831  * This includes libusb_handle_events() and its variants, and all the
834  * \section Using libusb_handle_events() from multiple threads
836  * Even when only using libusb_handle_events() and synchronous I/O functions,
838  * above with libusb_handle_events() like so:
844 		libusb_handle_events(ctx);
850  * libusb_handle_events() acquiring the events lock, so another thread
858  * libusb_handle_events() without worrying about locking. This is why
1597  * libusb_handle_events()) then you do not need to be concerned with this
1641  * libusb_handle_events()) then you do not need to be concerned with this
1750  * some other thread is event handling so calling libusb_handle_events() is not
1760  * libusb_handle_events()) then you do not need to be concerned with this
2197 int API_EXPORTED libusb_handle_events(libusb_context *ctx)
2208  * Like libusb_handle_events(), with the addition of a completed parameter
2235  * file descriptors (as opposed to using libusb_handle_events() or similar).
2304  * are calling libusb_handle_events() or a variant directly.