Lines Matching refs:libusb_handle_events
504 * 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
773 * This includes libusb_handle_events() and its variants, and all the
776 * \section Using libusb_handle_events() from multiple threads
778 * Even when only using libusb_handle_events() and synchronous I/O functions,
780 * above with libusb_handle_events() like so:
786 libusb_handle_events(ctx);
792 * libusb_handle_events() acquiring the events lock, so another thread
800 * libusb_handle_events() without worrying about locking. This is why
1603 * libusb_handle_events()) then you do not need to be concerned with this
1646 * libusb_handle_events()) then you do not need to be concerned with this
1755 * some other thread is event handling so calling libusb_handle_events() is not
1765 * libusb_handle_events()) then you do not need to be concerned with this
2178 int API_EXPORTED libusb_handle_events(libusb_context *ctx)
2189 * Like libusb_handle_events(), with the addition of a completed parameter
2216 * file descriptors (as opposed to using libusb_handle_events() or similar).
2285 * are calling libusb_handle_events() or a variant directly.
