Searched defs:libusb_handle_events (Results 1 - 2 of 2) sorted by path

/external/chromium_org/third_party/libusb/src/libusb/
H A Dio.c503 * 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(ct
2197 int API_EXPORTED libusb_handle_events(libusb_context *ctx) function
[all...]
/external/libusb/libusb/
H A Dio.c504 * This gives rise to the libusb_handle_events() function which your
511 * -# Periodically call libusb_handle_events() in non-blocking mode at fixed
513 * -# Repeatedly call libusb_handle_events() in blocking mode from a dedicated
529 * libusb_handle_events().
574 libusb_handle_events(ctx);
580 * sets of file descriptors or handling timeouts. libusb_handle_events() will
769 * This includes libusb_handle_events() and all the synchronous I/O functions -
1434 * libusb_handle_events()) then you do not need to be concerned with this
1477 * libusb_handle_events()) then you do not need to be concerned with this
1586 * some other thread is event handling so calling libusb_handle_events() i
1976 API_EXPORTED int libusb_handle_events(libusb_context *ctx) function
[all...]

Completed in 265 milliseconds