2 * I/O functions for libusb
3 * Copyright (C) 2007-2008 Daniel Drake <dsd@gentoo.org>
4 * Copyright (c) 2001 Johannes Erdfelt <johannes@erdfelt.com>
6 * This library is free software; you can redistribute it and/or
7 * modify it under the terms of the GNU Lesser General Public
8 * License as published by the Free Software Foundation; either
9 * version 2.1 of the License, or (at your option) any later version.
11 * This library is distributed in the hope that it will be useful,
12 * but WITHOUT ANY WARRANTY; without even the implied warranty of
13 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
14 * Lesser General Public License for more details.
16 * You should have received a copy of the GNU Lesser General Public
17 * License along with this library; if not, write to the Free Software
18 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
29 #include <sys/select.h>
36 /* this is a list of in-flight transfer handles, sorted by timeout expiration.
37 * URBs to timeout the soonest are placed at the beginning of the list, URBs
38 * that will time out later are placed after, and urbs with infinite timeout
39 * are always placed at the very end. */
40 static struct list_head flying_transfers;
41 static pthread_mutex_t flying_transfers_lock = PTHREAD_MUTEX_INITIALIZER;
43 /* list of poll fd's */
44 static struct list_head pollfds;
45 static pthread_mutex_t pollfds_lock = PTHREAD_MUTEX_INITIALIZER;
47 /* user callbacks for pollfd changes */
48 static libusb_pollfd_added_cb fd_added_cb = NULL;
49 static libusb_pollfd_removed_cb fd_removed_cb = NULL;
52 * \page io Synchronous and asynchronous device I/O
54 * \section intro Introduction
56 * If you're using libusb in your application, you're probably wanting to
57 * perform I/O with devices - you want to perform USB data transfers.
59 * libusb offers two separate interfaces for device I/O. This page aims to
60 * introduce the two in order to help you decide which one is more suitable
61 * for your application. You can also choose to use both interfaces in your
62 * application by considering each transfer on a case-by-case basis.
64 * Once you have read through the following discussion, you should consult the
65 * detailed API documentation pages for the details:
69 * \section theory Transfers at a logical level
71 * At a logical level, USB transfers typically happen in two parts. For
72 * example, when reading data from a endpoint:
73 * -# A request for data is sent to the device
74 * -# Some time later, the incoming data is received by the host
76 * or when writing data to an endpoint:
78 * -# The data is sent to the device
79 * -# Some time later, the host receives acknowledgement from the device that
80 * the data has been transferred.
82 * There may be an indefinite delay between the two steps. Consider a
83 * fictional USB input device with a button that the user can press. In order
84 * to determine when the button is pressed, you would likely submit a request
85 * to read data on a bulk or interrupt endpoint and wait for data to arrive.
86 * Data will arrive when the button is pressed by the user, which is
87 * potentially hours later.
89 * libusb offers both a synchronous and an asynchronous interface to performing
90 * USB transfers. The main difference is that the synchronous interface
91 * combines both steps indicated above into a single function call, whereas
92 * the asynchronous interface separates them.
94 * \section sync The synchronous interface
96 * The synchronous I/O interface allows you to perform a USB transfer with
97 * a single function call. When the function call returns, the transfer has
98 * completed and you can parse the results.
100 * If you have used the libusb-0.1 before, this I/O style will seem familar to
101 * you. libusb-0.1 only offered a synchronous interface.
103 * In our input device example, to read button presses you might write code
104 * in the following style:
106 unsigned char data[4];
108 int r = libusb_bulk_transfer(handle, EP_IN, data, sizeof(data), &actual_length, 0);
109 if (r == 0 && actual_length == sizeof(data)) {
110 // results of the transaction can now be found in the data buffer
111 // parse them here and report button press
117 * The main advantage of this model is simplicity: you did everything with
118 * a single simple function call.
120 * However, this interface has its limitations. Your application will sleep
121 * inside libusb_bulk_transfer() until the transaction has completed. If it
122 * takes the user 3 hours to press the button, your application will be
123 * sleeping for that long. Execution will be tied up inside the library -
124 * the entire thread will be useless for that duration.
126 * Another issue is that by tieing up the thread with that single transaction
127 * there is no possibility of performing I/O with multiple endpoints and/or
128 * multiple devices simultaneously, unless you resort to creating one thread
131 * Additionally, there is no opportunity to cancel the transfer after the
132 * request has been submitted.
134 * For details on how to use the synchronous API, see the
135 * \ref syncio "synchronous I/O API documentation" pages.
137 * \section async The asynchronous interface
139 * Asynchronous I/O is the most significant new feature in libusb-1.0.
140 * Although it is a more complex interface, it solves all the issues detailed
143 * Instead of providing which functions that block until the I/O has complete,
144 * libusb's asynchronous interface presents non-blocking functions which
145 * begin a transfer and then return immediately. Your application passes a
146 * callback function pointer to this non-blocking function, which libusb will
147 * call with the results of the transaction when it has completed.
149 * Transfers which have been submitted through the non-blocking functions
150 * can be cancelled with a separate function call.
152 * The non-blocking nature of this interface allows you to be simultaneously
153 * performing I/O to multiple endpoints on multiple devices, without having
156 * This added flexibility does come with some complications though:
157 * - In the interest of being a lightweight library, libusb does not create
158 * threads and can only operate when your application is calling into it. Your
159 * application must call into libusb from it's main loop when events are ready
160 * to be handled, or you must use some other scheme to allow libusb to
161 * undertake whatever work needs to be done.
162 * - libusb also needs to be called into at certain fixed points in time in
163 * order to accurately handle transfer timeouts.
164 * - Memory handling becomes more complex. You cannot use stack memory unless
165 * the function with that stack is guaranteed not to return until the transfer
166 * callback has finished executing.
167 * - You generally lose some linearity from your code flow because submitting
168 * the transfer request is done in a separate function from where the transfer
169 * results are handled. This becomes particularly obvious when you want to
170 * submit a second transfer based on the results of an earlier transfer.
172 * Internally, libusb's synchronous interface is expressed in terms of function
173 * calls to the asynchronous interface.
175 * For details on how to use the asynchronous API, see the
176 * \ref asyncio "asynchronous I/O API" documentation pages.
180 * @defgroup asyncio Asynchronous device I/O
182 * This page details libusb's asynchronous (non-blocking) API for USB device
183 * I/O. This interface is very powerful but is also quite complex - you will
184 * need to read this page carefully to understand the necessary considerations
185 * and issues surrounding use of this interface. Simplistic applications
186 * may wish to consider the \ref syncio "synchronous I/O API" instead.
188 * The asynchronous interface is built around the idea of separating transfer
189 * submission and handling of transfer completion (the synchronous model
190 * combines both of these into one). There may be a long delay between
191 * submission and completion, however the asynchronous submission function
192 * is non-blocking so will return control to your application during that
193 * potentially long delay.
195 * \section asyncabstraction Transfer abstraction
197 * For the asynchronous I/O, libusb implements the concept of a generic
198 * transfer entity for all types of I/O (control, bulk, interrupt,
199 * isochronous). The generic transfer object must be treated slightly
200 * differently depending on which type of I/O you are performing with it.
202 * This is represented by the public libusb_transfer structure type.
204 * \section asynctrf Asynchronous transfers
206 * We can view asynchronous I/O as a 5 step process:
210 * -# Completion handling
213 * \subsection asyncalloc Allocation
215 * This step involves allocating memory for a USB transfer. This is the
216 * generic transfer object mentioned above. At this stage, the transfer
217 * is "blank" with no details about what type of I/O it will be used for.
219 * Allocation is done with the libusb_alloc_transfer() function. You must use
220 * this function rather than allocating your own transfers.
222 * \subsection asyncfill Filling
224 * This step is where you take a previously allocated transfer and fill it
225 * with information to determine the message type and direction, data buffer,
226 * callback function, etc.
228 * You can either fill the required fields yourself or you can use the
229 * helper functions: libusb_fill_control_transfer(), libusb_fill_bulk_transfer()
230 * and libusb_fill_interrupt_transfer().
232 * \subsection asyncsubmit Submission
234 * When you have allocated a transfer and filled it, you can submit it using
235 * libusb_submit_transfer(). This function returns immediately but can be
236 * regarded as firing off the I/O request in the background.
238 * \subsection asynccomplete Completion handling
240 * After a transfer has been submitted, one of four things can happen to it:
242 * - The transfer completes (i.e. some data was transferred)
243 * - The transfer has a timeout and the timeout expires before all data is
245 * - The transfer fails due to an error
246 * - The transfer is cancelled
248 * Each of these will cause the user-specified transfer callback function to
249 * be invoked. It is up to the callback function to determine which of the
250 * above actually happened and to act accordingly.
252 * \subsection Deallocation
254 * When a transfer has completed (i.e. the callback function has been invoked),
255 * you are advised to free the transfer (unless you wish to resubmit it, see
256 * below). Transfers are deallocated with libusb_free_transfer().
258 * It is undefined behaviour to free a transfer which has not completed.
260 * \section asyncresubmit Resubmission
262 * You may be wondering why allocation, filling, and submission are all
263 * separated above where they could reasonably be combined into a single
266 * The reason for separation is to allow you to resubmit transfers without
267 * having to allocate new ones every time. This is especially useful for
268 * common situations dealing with interrupt endpoints - you allocate one
269 * transfer, fill and submit it, and when it returns with results you just
270 * resubmit it for the next interrupt.
272 * \section asynccancel Cancellation
274 * Another advantage of using the asynchronous interface is that you have
275 * the ability to cancel transfers which have not yet completed. This is
276 * done by calling the libusb_cancel_transfer() function.
278 * libusb_cancel_transfer() is asynchronous/non-blocking in itself. When the
279 * cancellation actually completes, the transfer's callback function will
280 * be invoked, and the callback function should check the transfer status to
281 * determine that it was cancelled.
283 * Freeing the transfer after it has been cancelled but before cancellation
284 * has completed will result in undefined behaviour.
286 * \section asyncctrl Considerations for control transfers
288 * The <tt>libusb_transfer</tt> structure is generic and hence does not
289 * include specific fields for the control-specific setup packet structure.
291 * In order to perform a control transfer, you must place the 8-byte setup
292 * packet at the start of the data buffer. To simplify this, you could
293 * cast the buffer pointer to type struct libusb_control_setup, or you can
294 * use the helper function libusb_fill_control_setup().
296 * The wLength field placed in the setup packet must be the length you would
297 * expect to be sent in the setup packet: the length of the payload that
298 * follows (or the expected maximum number of bytes to receive). However,
299 * the length field of the libusb_transfer object must be the length of
300 * the data buffer - i.e. it should be wLength <em>plus</em> the size of
301 * the setup packet (LIBUSB_CONTROL_SETUP_SIZE).
303 * If you use the helper functions, this is simplified for you:
304 * -# Allocate a buffer of size LIBUSB_CONTROL_SETUP_SIZE plus the size of the
305 * data you are sending/requesting.
306 * -# Call libusb_fill_control_setup() on the data buffer, using the transfer
307 * request size as the wLength value (i.e. do not include the extra space you
308 * allocated for the control setup).
309 * -# If this is a host-to-device transfer, place the data to be transferred
310 * in the data buffer, starting at offset LIBUSB_CONTROL_SETUP_SIZE.
311 * -# Call libusb_fill_control_transfer() to associate the data buffer with
312 * the transfer (and to set the remaining details such as callback and timeout).
313 * - Note that there is no parameter to set the length field of the transfer.
314 * The length is automatically inferred from the wLength field of the setup
316 * -# Submit the transfer.
318 * Further considerations are needed when handling transfer completion in
319 * your callback function:
320 * - As you might expect, the setup packet will still be sitting at the start
321 * of the data buffer.
322 * - If this was a device-to-host transfer, the received data will be sitting
323 * at offset LIBUSB_CONTROL_SETUP_SIZE into the buffer.
324 * - The actual_length field of the transfer structure is relative to the
325 * wLength of the setup packet, rather than the size of the data buffer. So,
326 * if your wLength was 4, your transfer's <tt>length</tt> was 12, then you
327 * should expect an <tt>actual_length</tt> of 4 to indicate that the data was
328 * transferred in entirity.
330 * To simplify parsing of setup packets and obtaining the data from the
331 * correct offset, you may wish to use the libusb_control_transfer_get_data()
332 * and libusb_control_transfer_get_setup() functions within your transfer
335 * Even though control endpoints do not halt, a completed control transfer
336 * may have a LIBUSB_TRANSFER_STALL status code. This indicates the control
337 * request was not supported.
339 * \section asyncintr Considerations for interrupt transfers
341 * All interrupt transfers are performed using the polling interval presented
342 * by the bInterval value of the endpoint descriptor.
344 * \section asynciso Considerations for isochronous transfers
346 * As isochronous transfers are more complicated than transfers to
347 * non-isochronous endpoints.
349 * To perform I/O to an isochronous endpoint, allocate the transfer by calling
350 * libusb_alloc_transfer() with an appropriate number of isochronous packets.
352 * During filling, set \ref libusb_transfer::type "type" to
353 * \ref libusb_transfer_type::LIBUSB_TRANSFER_TYPE_ISOCHRONOUS
354 * "LIBUSB_TRANSFER_TYPE_ISOCHRONOUS", and set
355 * \ref libusb_transfer::num_iso_packets "num_iso_packets" to a value less than
356 * or equal to the number of packets you requested during allocation.
357 * libusb_alloc_transfer() does not set either of these fields for you, given
358 * that you might not even use the transfer on an isochronous endpoint.
360 * Next, populate the length field for the first num_iso_packets entries in
361 * the \ref libusb_transfer::iso_packet_desc "iso_packet_desc" array. Section
362 * 5.6.3 of the USB2 specifications describe how the maximum isochronous
363 * packet length is determined by the endpoint descriptor. FIXME need a helper
364 * function to find this.
365 * FIXME, write a helper function to set the length for all iso packets in an
368 * For outgoing transfers, you'll obviously fill the buffer and populate the
369 * packet descriptors in hope that all the data gets transferred. For incoming
370 * transfers, you must ensure the buffer has sufficient capacity for
371 * the situation where all packets transfer the full amount of requested data.
373 * Completion handling requires some extra consideration. The
374 * \ref libusb_transfer::actual_length "actual_length" field of the transfer
375 * is meaningless and should not be examined; instead you must refer to the
376 * \ref libusb_iso_packet_descriptor::actual_length "actual_length" field of
377 * each individual packet.
379 * The \ref libusb_transfer::status "status" field of the transfer is also a
381 * - If the packets were submitted and the isochronous data microframes
382 * completed normally, status will have value
383 * \ref libusb_transfer_status::LIBUSB_TRANSFER_COMPLETED
384 * "LIBUSB_TRANSFER_COMPLETED". Note that bus errors and software-incurred
385 * delays are not counted as transfer errors; the transfer.status field may
386 * indicate COMPLETED even if some or all of the packets failed. Refer to
387 * the \ref libusb_iso_packet_descriptor::status "status" field of each
388 * individual packet to determine packet failures.
389 * - The status field will have value
390 * \ref libusb_transfer_status::LIBUSB_TRANSFER_ERROR
391 * "LIBUSB_TRANSFER_ERROR" only when serious errors were encountered.
392 * - Other transfer status codes occur with normal behaviour.
394 * The data for each packet will be found at an offset into the buffer that
395 * can be calculated as if each prior packet completed in full. FIXME write
396 * a helper function to determine this, and flesh this description out a bit
399 * \section asyncmem Memory caveats
401 * In most circumstances, it is not safe to use stack memory for transfer
402 * buffers. This is because the function that fired off the asynchronous
403 * transfer may return before libusb has finished using the buffer, and when
404 * the function returns it's stack gets destroyed. This is true for both
405 * host-to-device and device-to-host transfers.
407 * The only case in which it is safe to use stack memory is where you can
408 * guarantee that the function owning the stack space for the buffer does not
409 * return until after the transfer's callback function has completed. In every
410 * other case, you need to use heap memory instead.
412 * \section asyncflags Fine control
414 * Through using this asynchronous interface, you may find yourself repeating
415 * a few simple operations many times. You can apply a bitwise OR of certain
416 * flags to a transfer to simplify certain things:
417 * - \ref libusb_transfer_flags::LIBUSB_TRANSFER_SHORT_NOT_OK
418 * "LIBUSB_TRANSFER_SHORT_NOT_OK" results in transfers which transferred
419 * less than the requested amount of data being marked with status
420 * \ref libusb_transfer_status::LIBUSB_TRANSFER_ERROR "LIBUSB_TRANSFER_ERROR"
421 * (they would normally be regarded as COMPLETED)
422 * - \ref libusb_transfer_flags::LIBUSB_TRANSFER_FREE_BUFFER
423 * "LIBUSB_TRANSFER_FREE_BUFFER" allows you to ask libusb to free the transfer
424 * buffer when freeing the transfer.
425 * - \ref libusb_transfer_flags::LIBUSB_TRANSFER_FREE_TRANSFER
426 * "LIBUSB_TRANSFER_FREE_TRANSFER" causes libusb to automatically free the
427 * transfer after the transfer callback returns.
429 * \section asyncevent Event handling
431 * In accordance of the aim of being a lightweight library, libusb does not
432 * create threads internally. This means that libusb code does not execute
433 * at any time other than when your application is calling a libusb function.
434 * However, an asynchronous model requires that libusb perform work at various
435 * points in time - namely processing the results of previously-submitted
436 * transfers and invoking the user-supplied callback function.
438 * This gives rise to the libusb_handle_events() function which your
439 * application must call into when libusb has work do to. This gives libusb
440 * the opportunity to reap pending transfers, invoke callbacks, etc.
442 * The first issue to discuss here is how your application can figure out
443 * when libusb has work to do. In fact, there are two naive options which
444 * do not actually require your application to know this:
445 * -# Periodically call libusb_handle_events() in non-blocking mode at fixed
446 * short intervals from your main loop
447 * -# Repeatedly call libusb_handle_events() in blocking mode from a dedicated
450 * The first option is plainly not very nice, and will cause unnecessary
451 * CPU wakeups leading to increased power usage and decreased battery life.
452 * The second option is not very nice either, but may be the nicest option
453 * available to you if the "proper" approach can not be applied to your
454 * application (read on...).
456 * The recommended option is to integrate libusb with your application main
457 * event loop. libusb exposes a set of file descriptors which allow you to do
458 * this. Your main loop is probably already calling poll() or select() or a
459 * variant on a set of file descriptors for other event sources (e.g. keyboard
460 * button presses, mouse movements, network sockets, etc). You then add
461 * libusb's file descriptors to your poll()/select() calls, and when activity
462 * is detected on such descriptors you know it is time to call
463 * libusb_handle_events().
465 * There is one final event handling complication. libusb supports
466 * asynchronous transfers which time out after a specified time period, and
467 * this requires that libusb is called into at or after the timeout so that
468 * the timeout can be handled. So, in addition to considering libusb's file
469 * descriptors in your main event loop, you must also consider that libusb
470 * sometimes needs to be called into at fixed points in time even when there
471 * is no file descriptor activity.
473 * For the details on retrieving the set of file descriptors and determining
474 * the next timeout, see the \ref poll "polling and timing" API documentation.
478 * @defgroup poll Polling and timing
480 * This page documents libusb's functions for polling events and timing.
481 * These functions are only necessary for users of the
482 * \ref asyncio "asynchronous API". If you are only using the simpler
483 * \ref syncio "synchronous API" then you do not need to ever call these
486 * The justification for the functionality described here has already been
487 * discussed in the \ref asyncevent "event handling" section of the
488 * asynchronous API documentation. In summary, libusb does not create internal
489 * threads for event processing and hence relies on your application calling
490 * into libusb at certain points in time so that pending events can be handled.
491 * In order to know precisely when libusb needs to be called into, libusb
492 * offers you a set of pollable file descriptors and information about when
493 * the next timeout expires.
495 * If you are using the asynchronous I/O API, you must take one of the two
496 * following options, otherwise your I/O will not complete.
498 * \section pollsimple The simple option
500 * If your application revolves solely around libusb and does not need to
501 * handle other event sources, you can have a program structure as follows:
504 // find and open device
505 // maybe fire off some initial async I/O
507 while (user_has_not_requested_exit)
508 libusb_handle_events();
513 * With such a simple main loop, you do not have to worry about managing
514 * sets of file descriptors or handling timeouts. libusb_handle_events() will
515 * handle those details internally.
517 * \section pollmain The more advanced option
519 * In more advanced applications, you will already have a main loop which
520 * is monitoring other event sources: network sockets, X11 events, mouse
521 * movements, etc. Through exposing a set of file descriptors, libusb is
522 * designed to cleanly integrate into such main loops.
524 * In addition to polling file descriptors for the other event sources, you
525 * take a set of file descriptors from libusb and monitor those too. When you
526 * detect activity on libusb's file descriptors, you call
527 * libusb_handle_events_timeout() in non-blocking mode.
529 * You must also consider the fact that libusb sometimes has to handle events
530 * at certain known times which do not generate activity on file descriptors.
531 * Your main loop must also consider these times, modify it's poll()/select()
532 * timeout accordingly, and track time so that libusb_handle_events_timeout()
533 * is called in non-blocking mode when timeouts expire.
535 * In pseudo-code, you want something that looks like:
540 while (user has not requested application exit) {
541 libusb_get_next_timeout();
542 select(on libusb file descriptors plus any other event sources of interest,
543 using a timeout no larger than the value libusb just suggested)
544 if (select() indicated activity on libusb file descriptors)
545 libusb_handle_events_timeout(0);
546 if (time has elapsed to or beyond the libusb timeout)
547 libusb_handle_events_timeout(0);
553 * The set of file descriptors that libusb uses as event sources may change
554 * during the life of your application. Rather than having to repeatedly
555 * call libusb_get_pollfds(), you can set up notification functions for when
556 * the file descriptor set changes using libusb_set_pollfd_notifiers().
562 list_init(&flying_transfers);
565 fd_removed_cb = NULL;
568 static int calculate_timeout(struct usbi_transfer *transfer)
571 struct timespec current_time;
572 unsigned int timeout =
573 __USBI_TRANSFER_TO_LIBUSB_TRANSFER(transfer)->timeout;
578 r = clock_gettime(CLOCK_MONOTONIC, ¤t_time);
580 usbi_err("failed to read monotonic clock, errno=%d", errno);
584 current_time.tv_sec += timeout / 1000;
585 current_time.tv_nsec += (timeout % 1000) * 1000000;
587 if (current_time.tv_nsec > 1000000000) {
588 current_time.tv_nsec -= 1000000000;
589 current_time.tv_sec++;
592 TIMESPEC_TO_TIMEVAL(&transfer->timeout, ¤t_time);
596 static void add_to_flying_list(struct usbi_transfer *transfer)
598 struct usbi_transfer *cur;
599 struct timeval *timeout = &transfer->timeout;
601 pthread_mutex_lock(&flying_transfers_lock);
603 /* if we have no other flying transfers, start the list with this one */
604 if (list_empty(&flying_transfers)) {
605 list_add(&transfer->list, &flying_transfers);
609 /* if we have infinite timeout, append to end of list */
610 if (!timerisset(timeout)) {
611 list_add_tail(&transfer->list, &flying_transfers);
615 /* otherwise, find appropriate place in list */
616 list_for_each_entry(cur, &flying_transfers, list) {
617 /* find first timeout that occurs after the transfer in question */
618 struct timeval *cur_tv = &cur->timeout;
620 if (!timerisset(cur_tv) || (cur_tv->tv_sec > timeout->tv_sec) ||
621 (cur_tv->tv_sec == timeout->tv_sec &&
622 cur_tv->tv_usec > timeout->tv_usec)) {
623 list_add_tail(&transfer->list, &cur->list);
628 /* otherwise we need to be inserted at the end */
629 list_add_tail(&transfer->list, &flying_transfers);
631 pthread_mutex_unlock(&flying_transfers_lock);
635 * Allocate a libusb transfer with a specified number of isochronous packet
636 * descriptors. The returned transfer is pre-initialized for you. When the new
637 * transfer is no longer needed, it should be freed with
638 * libusb_free_transfer().
640 * Transfers intended for non-isochronous endpoints (e.g. control, bulk,
641 * interrupt) should specify an iso_packets count of zero.
643 * For transfers intended for isochronous endpoints, specify an appropriate
644 * number of packet descriptors to be allocated as part of the transfer.
645 * The returned transfer is not specially initialized for isochronous I/O;
646 * you are still required to set the
647 * \ref libusb_transfer::num_iso_packets "num_iso_packets" and
648 * \ref libusb_transfer::type "type" fields accordingly.
650 * It is safe to allocate a transfer with some isochronous packets and then
651 * use it on a non-isochronous endpoint. If you do this, ensure that at time
652 * of submission, num_iso_packets is 0 and that type is set appropriately.
654 * \param iso_packets number of isochronous packet descriptors to allocate
655 * \returns a newly allocated transfer, or NULL on error
657 API_EXPORTED struct libusb_transfer *libusb_alloc_transfer(int iso_packets)
659 size_t os_alloc_size = usbi_backend->transfer_priv_size
660 + (usbi_backend->add_iso_packet_size * iso_packets);
661 int alloc_size = sizeof(struct usbi_transfer)
662 + sizeof(struct libusb_transfer)
663 + (sizeof(struct libusb_iso_packet_descriptor) * iso_packets)
665 struct usbi_transfer *itransfer = malloc(alloc_size);
669 memset(itransfer, 0, alloc_size);
670 itransfer->num_iso_packets = iso_packets;
671 return __USBI_TRANSFER_TO_LIBUSB_TRANSFER(itransfer);
675 * Free a transfer structure. This should be called for all transfers
676 * allocated with libusb_alloc_transfer().
678 * If the \ref libusb_transfer_flags::LIBUSB_TRANSFER_FREE_BUFFER
679 * "LIBUSB_TRANSFER_FREE_BUFFER" flag is set and the transfer buffer is
680 * non-NULL, this function will also free the transfer buffer using the
681 * standard system memory allocator (e.g. free()).
683 * It is legal to call this function with a NULL transfer. In this case,
684 * the function will simply return safely.
686 * \param transfer the transfer to free
688 API_EXPORTED void libusb_free_transfer(struct libusb_transfer *transfer)
690 struct usbi_transfer *itransfer;
694 if (transfer->flags & LIBUSB_TRANSFER_FREE_BUFFER && transfer->buffer)
695 free(transfer->buffer);
697 itransfer = __LIBUSB_TRANSFER_TO_USBI_TRANSFER(transfer);
702 * Submit a transfer. This function will fire off the USB transfer and then
703 * return immediately.
705 * It is undefined behaviour to submit a transfer that has already been
706 * submitted but has not yet completed.
708 * \param transfer the transfer to submit
709 * \returns 0 on success, or a LIBUSB_ERROR code on failure
711 API_EXPORTED int libusb_submit_transfer(struct libusb_transfer *transfer)
713 struct usbi_transfer *itransfer =
714 __LIBUSB_TRANSFER_TO_USBI_TRANSFER(transfer);
717 itransfer->transferred = 0;
718 r = calculate_timeout(itransfer);
720 return LIBUSB_ERROR_OTHER;
722 if (transfer->type == LIBUSB_TRANSFER_TYPE_CONTROL) {
723 struct libusb_control_setup *setup =
724 (struct libusb_control_setup *) transfer->buffer;
726 usbi_dbg("RQT=%02x RQ=%02x VAL=%04x IDX=%04x length=%d",
727 setup->bmRequestType, setup->bRequest, setup->wValue, setup->wIndex,
730 setup->wValue = cpu_to_le16(setup->wValue);
731 setup->wIndex = cpu_to_le16(setup->wIndex);
732 setup->wLength = cpu_to_le16(setup->wLength);
735 add_to_flying_list(itransfer);
736 r = usbi_backend->submit_transfer(itransfer);
738 pthread_mutex_lock(&flying_transfers_lock);
739 list_del(&itransfer->list);
740 pthread_mutex_unlock(&flying_transfers_lock);
747 * Asynchronously cancel a previously submitted transfer.
748 * It is undefined behaviour to call this function on a transfer that is
749 * already being cancelled or has already completed.
750 * This function returns immediately, but this does not indicate cancellation
751 * is complete. Your callback function will be invoked at some later time
752 * with a transfer status of
753 * \ref libusb_transfer_status::LIBUSB_TRANSFER_CANCELLED
754 * "LIBUSB_TRANSFER_CANCELLED."
756 * \param transfer the transfer to cancel
757 * \returns 0 on success
758 * \returns non-zero on error
760 API_EXPORTED int libusb_cancel_transfer(struct libusb_transfer *transfer)
762 struct usbi_transfer *itransfer =
763 __LIBUSB_TRANSFER_TO_USBI_TRANSFER(transfer);
767 r = usbi_backend->cancel_transfer(itransfer);
769 usbi_err("cancel transfer failed error %d", r);
773 void usbi_handle_transfer_completion(struct usbi_transfer *itransfer,
774 enum libusb_transfer_status status)
776 struct libusb_transfer *transfer =
777 __USBI_TRANSFER_TO_LIBUSB_TRANSFER(itransfer);
780 pthread_mutex_lock(&flying_transfers_lock);
781 list_del(&itransfer->list);
782 pthread_mutex_unlock(&flying_transfers_lock);
784 if (status == LIBUSB_TRANSFER_COMPLETED
785 && transfer->flags & LIBUSB_TRANSFER_SHORT_NOT_OK) {
786 int rqlen = transfer->length;
787 if (transfer->type == LIBUSB_TRANSFER_TYPE_CONTROL)
788 rqlen -= LIBUSB_CONTROL_SETUP_SIZE;
789 if (rqlen != itransfer->transferred) {
790 usbi_dbg("interpreting short transfer as error");
791 status = LIBUSB_TRANSFER_ERROR;
795 flags = transfer->flags;
796 transfer->status = status;
797 transfer->actual_length = itransfer->transferred;
798 if (transfer->callback)
799 transfer->callback(transfer);
800 /* transfer might have been freed by the above call, do not use from
802 if (flags & LIBUSB_TRANSFER_FREE_TRANSFER)
803 libusb_free_transfer(transfer);
806 void usbi_handle_transfer_cancellation(struct usbi_transfer *transfer)
808 /* if the URB was cancelled due to timeout, report timeout to the user */
809 if (transfer->flags & USBI_TRANSFER_TIMED_OUT) {
810 usbi_dbg("detected timeout cancellation");
811 usbi_handle_transfer_completion(transfer, LIBUSB_TRANSFER_TIMED_OUT);
815 /* otherwise its a normal async cancel */
816 usbi_handle_transfer_completion(transfer, LIBUSB_TRANSFER_CANCELLED);
819 static void handle_timeout(struct usbi_transfer *itransfer)
821 struct libusb_transfer *transfer =
822 __USBI_TRANSFER_TO_LIBUSB_TRANSFER(itransfer);
825 itransfer->flags |= USBI_TRANSFER_TIMED_OUT;
826 r = libusb_cancel_transfer(transfer);
828 usbi_warn("async cancel failed %d errno=%d", r, errno);
831 static int handle_timeouts(void)
833 struct timespec systime_ts;
834 struct timeval systime;
835 struct usbi_transfer *transfer;
838 pthread_mutex_lock(&flying_transfers_lock);
839 if (list_empty(&flying_transfers))
842 /* get current time */
843 r = clock_gettime(CLOCK_MONOTONIC, &systime_ts);
847 TIMESPEC_TO_TIMEVAL(&systime, &systime_ts);
849 /* iterate through flying transfers list, finding all transfers that
850 * have expired timeouts */
851 list_for_each_entry(transfer, &flying_transfers, list) {
852 struct timeval *cur_tv = &transfer->timeout;
854 /* if we've reached transfers of infinite timeout, we're all done */
855 if (!timerisset(cur_tv))
858 /* ignore timeouts we've already handled */
859 if (transfer->flags & USBI_TRANSFER_TIMED_OUT)
862 /* if transfer has non-expired timeout, nothing more to do */
863 if ((cur_tv->tv_sec > systime.tv_sec) ||
864 (cur_tv->tv_sec == systime.tv_sec &&
865 cur_tv->tv_usec > systime.tv_usec))
868 /* otherwise, we've got an expired timeout to handle */
869 handle_timeout(transfer);
873 pthread_mutex_unlock(&flying_transfers_lock);
877 static int handle_events(struct timeval *tv)
881 fd_set readfds, writefds;
882 fd_set *_readfds = NULL;
883 fd_set *_writefds = NULL;
884 struct usbi_pollfd *ipollfd;
885 int have_readfds = 0;
886 int have_writefds = 0;
887 struct timeval select_timeout;
888 struct timeval timeout;
890 r = libusb_get_next_timeout(&timeout);
892 /* timeout already expired? */
893 if (!timerisset(&timeout))
894 return handle_timeouts();
896 /* choose the smallest of next URB timeout or user specified timeout */
897 if (timercmp(&timeout, tv, <))
898 select_timeout = timeout;
900 select_timeout = *tv;
902 select_timeout = *tv;
907 pthread_mutex_lock(&pollfds_lock);
908 list_for_each_entry(ipollfd, &pollfds, list) {
909 struct libusb_pollfd *pollfd = &ipollfd->pollfd;
911 if (pollfd->events & POLLIN) {
913 FD_SET(fd, &readfds);
915 if (pollfd->events & POLLOUT) {
917 FD_SET(fd, &writefds);
922 pthread_mutex_unlock(&pollfds_lock);
927 _writefds = &writefds;
929 usbi_dbg("select() with timeout in %d.%06ds", select_timeout.tv_sec,
930 select_timeout.tv_usec);
931 r = select(maxfd + 1, _readfds, _writefds, NULL, &select_timeout);
932 usbi_dbg("select() returned %d with %d.%06ds remaining",
933 r, select_timeout.tv_sec, select_timeout.tv_usec);
935 *tv = select_timeout;
936 return handle_timeouts();
937 } else if (r == -1 && errno == EINTR) {
940 usbi_err("select failed %d err=%d\n", r, errno);
941 return LIBUSB_ERROR_IO;
944 r = usbi_backend->handle_events(_readfds, _writefds);
946 usbi_err("backend handle_events failed with error %d", r);
952 * Handle any pending events.
954 * libusb determines "pending events" by checking if any timeouts have expired
955 * and by checking the set of file descriptors for activity.
957 * If a zero timeval is passed, this function will handle any already-pending
958 * events and then immediately return in non-blocking style.
960 * If a non-zero timeval is passed and no events are currently pending, this
961 * function will block waiting for events to handle up until the specified
962 * timeout. If an event arrives or a signal is raised, this function will
965 * \param tv the maximum time to block waiting for events, or zero for
967 * \returns 0 on success, or a LIBUSB_ERROR code on failure
969 API_EXPORTED int libusb_handle_events_timeout(struct timeval *tv)
971 return handle_events(tv);
975 * Handle any pending events in blocking mode with a sensible timeout. This
976 * timeout is currently hardcoded at 2 seconds but we may change this if we
977 * decide other values are more sensible. For finer control over whether this
978 * function is blocking or non-blocking, or the maximum timeout, use
979 * libusb_handle_events_timeout() instead.
981 * \returns 0 on success, or a LIBUSB_ERROR code on failure
983 API_EXPORTED int libusb_handle_events(void)
988 return handle_events(&tv);
992 * Determine the next internal timeout that libusb needs to handle. You only
993 * need to use this function if you are calling poll() or select() or similar
994 * on libusb's file descriptors yourself - you do not need to use it if you
995 * are calling libusb_handle_events() or a variant directly.
997 * You should call this function in your main loop in order to determine how
998 * long to wait for select() or poll() to return results. libusb needs to be
999 * called into at this timeout, so you should use it as an upper bound on
1000 * your select() or poll() call.
1002 * When the timeout has expired, call into libusb_handle_events_timeout()
1003 * (perhaps in non-blocking mode) so that libusb can handle the timeout.
1005 * This function may return 1 (success) and an all-zero timeval. If this is
1006 * the case, it indicates that libusb has a timeout that has already expired
1007 * so you should call libusb_handle_events_timeout() or similar immediately.
1008 * A return code of 0 indicates that there are no pending timeouts.
1010 * \param tv output location for a relative time against the current
1011 * clock in which libusb must be called into in order to process timeout events
1012 * \returns 0 if there are no pending timeouts, 1 if a timeout was returned,
1013 * or LIBUSB_ERROR_OTHER on failure
1015 API_EXPORTED int libusb_get_next_timeout(struct timeval *tv)
1017 struct usbi_transfer *transfer;
1018 struct timespec cur_ts;
1019 struct timeval cur_tv;
1020 struct timeval *next_timeout;
1024 pthread_mutex_lock(&flying_transfers_lock);
1025 if (list_empty(&flying_transfers)) {
1026 pthread_mutex_unlock(&flying_transfers_lock);
1027 usbi_dbg("no URBs, no timeout!");
1031 /* find next transfer which hasn't already been processed as timed out */
1032 list_for_each_entry(transfer, &flying_transfers, list) {
1033 if (!(transfer->flags & USBI_TRANSFER_TIMED_OUT)) {
1038 pthread_mutex_unlock(&flying_transfers_lock);
1041 usbi_dbg("all URBs have already been processed for timeouts");
1045 next_timeout = &transfer->timeout;
1047 /* no timeout for next transfer */
1048 if (!timerisset(next_timeout)) {
1049 usbi_dbg("no URBs with timeouts, no timeout!");
1053 r = clock_gettime(CLOCK_MONOTONIC, &cur_ts);
1055 usbi_err("failed to read monotonic clock, errno=%d", errno);
1056 return LIBUSB_ERROR_OTHER;
1058 TIMESPEC_TO_TIMEVAL(&cur_tv, &cur_ts);
1060 if (timercmp(&cur_tv, next_timeout, >=)) {
1061 usbi_dbg("first timeout already expired");
1064 timersub(next_timeout, &cur_tv, tv);
1065 usbi_dbg("next timeout in %d.%06ds", tv->tv_sec, tv->tv_usec);
1072 * Register notification functions for file descriptor additions/removals.
1073 * These functions will be invoked for every new or removed file descriptor
1074 * that libusb uses as an event source.
1076 * To remove notifiers, pass NULL values for the function pointers.
1078 * \param added_cb pointer to function for addition notifications
1079 * \param removed_cb pointer to function for removal notifications
1081 API_EXPORTED void libusb_set_pollfd_notifiers(libusb_pollfd_added_cb added_cb,
1082 libusb_pollfd_removed_cb removed_cb)
1084 fd_added_cb = added_cb;
1085 fd_removed_cb = removed_cb;
1088 int usbi_add_pollfd(int fd, short events)
1090 struct usbi_pollfd *ipollfd = malloc(sizeof(*ipollfd));
1094 usbi_dbg("add fd %d events %d", fd, events);
1095 ipollfd->pollfd.fd = fd;
1096 ipollfd->pollfd.events = events;
1097 pthread_mutex_lock(&pollfds_lock);
1098 list_add(&ipollfd->list, &pollfds);
1099 pthread_mutex_unlock(&pollfds_lock);
1102 fd_added_cb(fd, events);
1106 void usbi_remove_pollfd(int fd)
1108 struct usbi_pollfd *ipollfd;
1111 usbi_dbg("remove fd %d", fd);
1112 pthread_mutex_lock(&pollfds_lock);
1113 list_for_each_entry(ipollfd, &pollfds, list)
1114 if (ipollfd->pollfd.fd == fd) {
1120 usbi_err("couldn't find fd %d to remove", fd);
1121 pthread_mutex_unlock(&pollfds_lock);
1125 list_del(&ipollfd->list);
1126 pthread_mutex_unlock(&pollfds_lock);
1133 * Retrieve a list of file descriptors that should be polled by your main loop
1134 * as libusb event sources.
1136 * The returned list is NULL-terminated and should be freed with free() when
1137 * done. The actual list contents must not be touched.
1139 * \returns a NULL-terminated list of libusb_pollfd structures, or NULL on
1142 API_EXPORTED const struct libusb_pollfd **libusb_get_pollfds(void)
1144 struct libusb_pollfd **ret = NULL;
1145 struct usbi_pollfd *ipollfd;
1149 pthread_mutex_lock(&pollfds_lock);
1150 list_for_each_entry(ipollfd, &pollfds, list)
1153 ret = calloc(cnt + 1, sizeof(struct libusb_pollfd *));
1157 list_for_each_entry(ipollfd, &pollfds, list)
1158 ret[i++] = (struct libusb_pollfd *) ipollfd;
1162 pthread_mutex_unlock(&pollfds_lock);
1163 return (const struct libusb_pollfd **) ret;