This page details libusb's asynchronous (non-blocking) API for USB device I/O. More...

Data Structures
struct	libusb_control_setup
	Setup packet for control transfers. More...
struct	libusb_iso_packet_descriptor
	Isochronous packet descriptor. More...
struct	libusb_transfer
	The generic USB transfer structure. More...

Typedefs
typedef void(*	libusb_transfer_cb_fn )(struct libusb_transfer *transfer)
	Asynchronous transfer callback function type.

Enumerations
enum	libusb_transfer_status { LIBUSB_TRANSFER_COMPLETED, LIBUSB_TRANSFER_ERROR, LIBUSB_TRANSFER_TIMED_OUT, LIBUSB_TRANSFER_CANCELLED, LIBUSB_TRANSFER_STALL, LIBUSB_TRANSFER_NO_DEVICE, LIBUSB_TRANSFER_OVERFLOW }
	Transfer status codes. More...
enum	libusb_transfer_flags { LIBUSB_TRANSFER_SHORT_NOT_OK = 1<<0, LIBUSB_TRANSFER_FREE_BUFFER = 1<<1, LIBUSB_TRANSFER_FREE_TRANSFER = 1<<2, LIBUSB_TRANSFER_ADD_ZERO_PACKET = 1 << 3 }
	libusb_transfer.flags values More...

Functions
struct libusb_transfer *	libusb_alloc_transfer (int iso_packets)
	Allocate a libusb transfer with a specified number of isochronous packet descriptors.
void	libusb_free_transfer (struct libusb_transfer *transfer)
	Free a transfer structure.
int	libusb_submit_transfer (struct libusb_transfer *transfer)
	Submit a transfer.
int	libusb_cancel_transfer (struct libusb_transfer *transfer)
	Asynchronously cancel a previously submitted transfer.
static unsigned char *	libusb_control_transfer_get_data (struct libusb_transfer *transfer)
	Get the data section of a control transfer.
static struct libusb_control_setup *	libusb_control_transfer_get_setup (struct libusb_transfer *transfer)
	Get the control setup packet of a control transfer.
static void	libusb_fill_control_setup (unsigned char *buffer, uint8_t bmRequestType, uint8_t bRequest, uint16_t wValue, uint16_t wIndex, uint16_t wLength)
	Helper function to populate the setup packet (first 8 bytes of the data buffer) for a control transfer.
static void	libusb_fill_control_transfer (struct libusb_transfer transfer, libusb_device_handle dev_handle, unsigned char buffer, libusb_transfer_cb_fn callback, void user_data, unsigned int timeout)
	Helper function to populate the required libusb_transfer fields for a control transfer.
static void	libusb_fill_bulk_transfer (struct libusb_transfer transfer, libusb_device_handle dev_handle, unsigned char endpoint, unsigned char buffer, int length, libusb_transfer_cb_fn callback, void user_data, unsigned int timeout)
	Helper function to populate the required libusb_transfer fields for a bulk transfer.
static void	libusb_fill_interrupt_transfer (struct libusb_transfer transfer, libusb_device_handle dev_handle, unsigned char endpoint, unsigned char buffer, int length, libusb_transfer_cb_fn callback, void user_data, unsigned int timeout)
	Helper function to populate the required libusb_transfer fields for an interrupt transfer.
static void	libusb_fill_iso_transfer (struct libusb_transfer transfer, libusb_device_handle dev_handle, unsigned char endpoint, unsigned char buffer, int length, int num_iso_packets, libusb_transfer_cb_fn callback, void user_data, unsigned int timeout)
	Helper function to populate the required libusb_transfer fields for an isochronous transfer.
static void	libusb_set_iso_packet_lengths (struct libusb_transfer *transfer, unsigned int length)
	Convenience function to set the length of all packets in an isochronous transfer, based on the num_iso_packets field in the transfer structure.
static unsigned char *	libusb_get_iso_packet_buffer (struct libusb_transfer *transfer, unsigned int packet)
	Convenience function to locate the position of an isochronous packet within the buffer of an isochronous transfer.
static unsigned char *	libusb_get_iso_packet_buffer_simple (struct libusb_transfer *transfer, unsigned int packet)
	Convenience function to locate the position of an isochronous packet within the buffer of an isochronous transfer, for transfers where each packet is of identical size.

Detailed Description

This page details libusb's asynchronous (non-blocking) API for USB device I/O.

This interface is very powerful but is also quite complex - you will need to read this page carefully to understand the necessary considerations and issues surrounding use of this interface. Simplistic applications may wish to consider the synchronous I/O API instead.

The asynchronous interface is built around the idea of separating transfer submission and handling of transfer completion (the synchronous model combines both of these into one). There may be a long delay between submission and completion, however the asynchronous submission function is non-blocking so will return control to your application during that potentially long delay.

Transfer abstraction

For the asynchronous I/O, libusb implements the concept of a generic transfer entity for all types of I/O (control, bulk, interrupt, isochronous). The generic transfer object must be treated slightly differently depending on which type of I/O you are performing with it.

This is represented by the public libusb_transfer structure type.

Asynchronous transfers

We can view asynchronous I/O as a 5 step process:

Allocation: allocate a libusb_transfer
Filling: populate the libusb_transfer instance with information about the transfer you wish to perform
Submission: ask libusb to submit the transfer
Completion handling: examine transfer results in the libusb_transfer structure
Deallocation: clean up resources

Allocation

This step involves allocating memory for a USB transfer. This is the generic transfer object mentioned above. At this stage, the transfer is "blank" with no details about what type of I/O it will be used for.

Allocation is done with the libusb_alloc_transfer() function. You must use this function rather than allocating your own transfers.

Filling

This step is where you take a previously allocated transfer and fill it with information to determine the message type and direction, data buffer, callback function, etc.

You can either fill the required fields yourself or you can use the helper functions: libusb_fill_control_transfer(), libusb_fill_bulk_transfer() and libusb_fill_interrupt_transfer().

Submission

When you have allocated a transfer and filled it, you can submit it using libusb_submit_transfer(). This function returns immediately but can be regarded as firing off the I/O request in the background.

Completion handling

After a transfer has been submitted, one of four things can happen to it:

The transfer completes (i.e. some data was transferred)
The transfer has a timeout and the timeout expires before all data is transferred
The transfer fails due to an error
The transfer is cancelled

Each of these will cause the user-specified transfer callback function to be invoked. It is up to the callback function to determine which of the above actually happened and to act accordingly.

The user-specified callback is passed a pointer to the libusb_transfer structure which was used to setup and submit the transfer. At completion time, libusb has populated this structure with results of the transfer: success or failure reason, number of bytes of data transferred, etc. See the libusb_transfer structure documentation for more information.

Deallocation

When a transfer has completed (i.e. the callback function has been invoked), you are advised to free the transfer (unless you wish to resubmit it, see below). Transfers are deallocated with libusb_free_transfer().

It is undefined behaviour to free a transfer which has not completed.

Resubmission

You may be wondering why allocation, filling, and submission are all separated above where they could reasonably be combined into a single operation.

The reason for separation is to allow you to resubmit transfers without having to allocate new ones every time. This is especially useful for common situations dealing with interrupt endpoints - you allocate one transfer, fill and submit it, and when it returns with results you just resubmit it for the next interrupt.

Cancellation

Another advantage of using the asynchronous interface is that you have the ability to cancel transfers which have not yet completed. This is done by calling the libusb_cancel_transfer() function.

libusb_cancel_transfer() is asynchronous/non-blocking in itself. When the cancellation actually completes, the transfer's callback function will be invoked, and the callback function should check the transfer status to determine that it was cancelled.

Freeing the transfer after it has been cancelled but before cancellation has completed will result in undefined behaviour.

When a transfer is cancelled, some of the data may have been transferred. libusb will communicate this to you in the transfer callback. Do not assume that no data was transferred.

Overflows on device-to-host bulk/interrupt endpoints

If your device does not have predictable transfer sizes (or it misbehaves), your application may submit a request for data on an IN endpoint which is smaller than the data that the device wishes to send. In some circumstances this will cause an overflow, which is a nasty condition to deal with. See the Packets and overflows page for discussion.

Considerations for control transfers

The libusb_transfer structure is generic and hence does not include specific fields for the control-specific setup packet structure.

In order to perform a control transfer, you must place the 8-byte setup packet at the start of the data buffer. To simplify this, you could cast the buffer pointer to type struct libusb_control_setup, or you can use the helper function libusb_fill_control_setup().

The wLength field placed in the setup packet must be the length you would expect to be sent in the setup packet: the length of the payload that follows (or the expected maximum number of bytes to receive). However, the length field of the libusb_transfer object must be the length of the data buffer - i.e. it should be wLength plus the size of the setup packet (LIBUSB_CONTROL_SETUP_SIZE).

If you use the helper functions, this is simplified for you:

Allocate a buffer of size LIBUSB_CONTROL_SETUP_SIZE plus the size of the data you are sending/requesting.
Call libusb_fill_control_setup() on the data buffer, using the transfer request size as the wLength value (i.e. do not include the extra space you allocated for the control setup).
If this is a host-to-device transfer, place the data to be transferred in the data buffer, starting at offset LIBUSB_CONTROL_SETUP_SIZE.
Call libusb_fill_control_transfer() to associate the data buffer with the transfer (and to set the remaining details such as callback and timeout).
- Note that there is no parameter to set the length field of the transfer. The length is automatically inferred from the wLength field of the setup packet.
Submit the transfer.

The multi-byte control setup fields (wValue, wIndex and wLength) must be given in little-endian byte order (the endianness of the USB bus). Endianness conversion is transparently handled by libusb_fill_control_setup() which is documented to accept host-endian values.

Further considerations are needed when handling transfer completion in your callback function:

As you might expect, the setup packet will still be sitting at the start of the data buffer.
If this was a device-to-host transfer, the received data will be sitting at offset LIBUSB_CONTROL_SETUP_SIZE into the buffer.
The actual_length field of the transfer structure is relative to the wLength of the setup packet, rather than the size of the data buffer. So, if your wLength was 4, your transfer's length was 12, then you should expect an actual_length of 4 to indicate that the data was transferred in entirity.

To simplify parsing of setup packets and obtaining the data from the correct offset, you may wish to use the libusb_control_transfer_get_data() and libusb_control_transfer_get_setup() functions within your transfer callback.

Even though control endpoints do not halt, a completed control transfer may have a LIBUSB_TRANSFER_STALL status code. This indicates the control request was not supported.

Considerations for interrupt transfers

All interrupt transfers are performed using the polling interval presented by the bInterval value of the endpoint descriptor.

Considerations for isochronous transfers

Isochronous transfers are more complicated than transfers to non-isochronous endpoints.

To perform I/O to an isochronous endpoint, allocate the transfer by calling libusb_alloc_transfer() with an appropriate number of isochronous packets.

During filling, set type to LIBUSB_TRANSFER_TYPE_ISOCHRONOUS, and set num_iso_packets to a value less than or equal to the number of packets you requested during allocation. libusb_alloc_transfer() does not set either of these fields for you, given that you might not even use the transfer on an isochronous endpoint.

Next, populate the length field for the first num_iso_packets entries in the iso_packet_desc array. Section 5.6.3 of the USB2 specifications describe how the maximum isochronous packet length is determined by the wMaxPacketSize field in the endpoint descriptor. Two functions can help you here:

libusb_get_max_iso_packet_size() is an easy way to determine the max packet size for an isochronous endpoint. Note that the maximum packet size is actually the maximum number of bytes that can be transmitted in a single microframe, therefore this function multiplies the maximum number of bytes per transaction by the number of transaction opportunities per microframe.
libusb_set_iso_packet_lengths() assigns the same length to all packets within a transfer, which is usually what you want.

For outgoing transfers, you'll obviously fill the buffer and populate the packet descriptors in hope that all the data gets transferred. For incoming transfers, you must ensure the buffer has sufficient capacity for the situation where all packets transfer the full amount of requested data.

Completion handling requires some extra consideration. The actual_length field of the transfer is meaningless and should not be examined; instead you must refer to the actual_length field of each individual packet.

The status field of the transfer is also a little misleading:

If the packets were submitted and the isochronous data microframes completed normally, status will have value LIBUSB_TRANSFER_COMPLETED. Note that bus errors and software-incurred delays are not counted as transfer errors; the transfer.status field may indicate COMPLETED even if some or all of the packets failed. Refer to the status field of each individual packet to determine packet failures.
The status field will have value LIBUSB_TRANSFER_ERROR only when serious errors were encountered.
Other transfer status codes occur with normal behaviour.

The data for each packet will be found at an offset into the buffer that can be calculated as if each prior packet completed in full. The libusb_get_iso_packet_buffer() and libusb_get_iso_packet_buffer_simple() functions may help you here.

Memory caveats

In most circumstances, it is not safe to use stack memory for transfer buffers. This is because the function that fired off the asynchronous transfer may return before libusb has finished using the buffer, and when the function returns it's stack gets destroyed. This is true for both host-to-device and device-to-host transfers.

The only case in which it is safe to use stack memory is where you can guarantee that the function owning the stack space for the buffer does not return until after the transfer's callback function has completed. In every other case, you need to use heap memory instead.

Fine control

Through using this asynchronous interface, you may find yourself repeating a few simple operations many times. You can apply a bitwise OR of certain flags to a transfer to simplify certain things:

LIBUSB_TRANSFER_SHORT_NOT_OK results in transfers which transferred less than the requested amount of data being marked with status LIBUSB_TRANSFER_ERROR (they would normally be regarded as COMPLETED)
LIBUSB_TRANSFER_FREE_BUFFER allows you to ask libusb to free the transfer buffer when freeing the transfer.
LIBUSB_TRANSFER_FREE_TRANSFER causes libusb to automatically free the transfer after the transfer callback returns.

Event handling

In accordance of the aim of being a lightweight library, libusb does not create threads internally. This means that libusb code does not execute at any time other than when your application is calling a libusb function. However, an asynchronous model requires that libusb perform work at various points in time - namely processing the results of previously-submitted transfers and invoking the user-supplied callback function.

This gives rise to the libusb_handle_events() function which your application must call into when libusb has work do to. This gives libusb the opportunity to reap pending transfers, invoke callbacks, etc.

The first issue to discuss here is how your application can figure out when libusb has work to do. In fact, there are two naive options which do not actually require your application to know this:

Periodically call libusb_handle_events() in non-blocking mode at fixed short intervals from your main loop
Repeatedly call libusb_handle_events() in blocking mode from a dedicated thread.

The first option is plainly not very nice, and will cause unnecessary CPU wakeups leading to increased power usage and decreased battery life. The second option is not very nice either, but may be the nicest option available to you if the "proper" approach can not be applied to your application (read on...).

The recommended option is to integrate libusb with your application main event loop. libusb exposes a set of file descriptors which allow you to do this. Your main loop is probably already calling poll() or select() or a variant on a set of file descriptors for other event sources (e.g. keyboard button presses, mouse movements, network sockets, etc). You then add libusb's file descriptors to your poll()/select() calls, and when activity is detected on such descriptors you know it is time to call libusb_handle_events().

There is one final event handling complication. libusb supports asynchronous transfers which time out after a specified time period, and this requires that libusb is called into at or after the timeout so that the timeout can be handled. So, in addition to considering libusb's file descriptors in your main event loop, you must also consider that libusb sometimes needs to be called into at fixed points in time even when there is no file descriptor activity.

For the details on retrieving the set of file descriptors and determining the next timeout, see the polling and timing API documentation.

Typedef Documentation

typedef void( * libusb_transfer_cb_fn)(struct libusb_transfer *transfer)

Asynchronous transfer callback function type.

When submitting asynchronous transfers, you pass a pointer to a callback function of this type via the callback member of the libusb_transfer structure. libusb will call this function later, when the transfer has completed or failed. See Asynchronous device I/O for more information.

Parameters:

transfer The libusb_transfer struct the callback function is being notified about.

Enumeration Type Documentation

enum libusb_transfer_status

Transfer status codes.

Enumerator:

LIBUSB_TRANSFER_COMPLETED	Transfer completed without error. Note that this does not indicate that the entire amount of requested data was transferred.
LIBUSB_TRANSFER_ERROR	Transfer failed.
LIBUSB_TRANSFER_TIMED_OUT	Transfer timed out.
LIBUSB_TRANSFER_CANCELLED	Transfer was cancelled.
LIBUSB_TRANSFER_STALL	For bulk/interrupt endpoints: halt condition detected (endpoint stalled). For control endpoints: control request not supported.
LIBUSB_TRANSFER_NO_DEVICE	Device was disconnected.
LIBUSB_TRANSFER_OVERFLOW	Device sent more data than requested.

enum libusb_transfer_flags

libusb_transfer.flags values

Enumerator:

LIBUSB_TRANSFER_SHORT_NOT_OK	Report short frames as errors.
LIBUSB_TRANSFER_FREE_BUFFER	Automatically free() transfer buffer during libusb_free_transfer()
LIBUSB_TRANSFER_FREE_TRANSFER	Automatically call libusb_free_transfer() after callback returns. If this flag is set, it is illegal to call libusb_free_transfer() from your transfer callback, as this will result in a double-free when this flag is acted upon.
LIBUSB_TRANSFER_ADD_ZERO_PACKET	Terminate transfers that are a multiple of the endpoint's wMaxPacketSize with an extra zero length packet. This is useful when a device protocol mandates that each logical request is terminated by an incomplete packet (i.e. the logical requests are not separated by other means). This flag only affects host-to-device transfers to bulk and interrupt endpoints. In other situations, it is ignored. This flag only affects transfers with a length that is a multiple of the endpoint's wMaxPacketSize. On transfers of other lengths, this flag has no effect. Therefore, if you are working with a device that needs a ZLP whenever the end of the logical request falls on a packet boundary, then it is sensible to set this flag on every transfer (you do not have to worry about only setting it on transfers that end on the boundary). This flag is currently only supported on Linux. On other systems, libusb_submit_transfer() will return LIBUSB_ERROR_NOT_SUPPORTED for every transfer where this flag is set. Available since libusb-1.0.9.

Function Documentation

struct libusb_transfer* libusb_alloc_transfer ( int iso_packets )

read

Allocate a libusb transfer with a specified number of isochronous packet descriptors.

The returned transfer is pre-initialized for you. When the new transfer is no longer needed, it should be freed with libusb_free_transfer().

Transfers intended for non-isochronous endpoints (e.g. control, bulk, interrupt) should specify an iso_packets count of zero.

For transfers intended for isochronous endpoints, specify an appropriate number of packet descriptors to be allocated as part of the transfer. The returned transfer is not specially initialized for isochronous I/O; you are still required to set the num_iso_packets and type fields accordingly.

It is safe to allocate a transfer with some isochronous packets and then use it on a non-isochronous endpoint. If you do this, ensure that at time of submission, num_iso_packets is 0 and that type is set appropriately.

Parameters:

iso_packets number of isochronous packet descriptors to allocate

Returns:: a newly allocated transfer, or NULL on error

void libusb_free_transfer ( struct libusb_transfer * transfer )

Free a transfer structure.

This should be called for all transfers allocated with libusb_alloc_transfer().

If the LIBUSB_TRANSFER_FREE_BUFFER flag is set and the transfer buffer is non-NULL, this function will also free the transfer buffer using the standard system memory allocator (e.g. free()).

It is legal to call this function with a NULL transfer. In this case, the function will simply return safely.

It is not legal to free an active transfer (one which has been submitted and has not yet completed).

Parameters:

transfer the transfer to free

int libusb_submit_transfer ( struct libusb_transfer * transfer )

Submit a transfer.

This function will fire off the USB transfer and then return immediately.

Parameters:

transfer the transfer to submit

Returns:: 0 on success; LIBUSB_ERROR_NO_DEVICE if the device has been disconnected; LIBUSB_ERROR_BUSY if the transfer has already been submitted.; LIBUSB_ERROR_NOT_SUPPORTED if the transfer flags are not supported by the operating system.; another LIBUSB_ERROR code on other failure

int libusb_cancel_transfer ( struct libusb_transfer * transfer )

Asynchronously cancel a previously submitted transfer.

This function returns immediately, but this does not indicate cancellation is complete. Your callback function will be invoked at some later time with a transfer status of LIBUSB_TRANSFER_CANCELLED.

Parameters:

transfer the transfer to cancel

Returns:: 0 on success; LIBUSB_ERROR_NOT_FOUND if the transfer is already complete or cancelled.; a LIBUSB_ERROR code on failure

static unsigned char* libusb_control_transfer_get_data ( struct libusb_transfer * transfer )

inlinestatic

Get the data section of a control transfer.

This convenience function is here to remind you that the data does not start until 8 bytes into the actual buffer, as the setup packet comes first.

Calling this function only makes sense from a transfer callback function, or situations where you have already allocated a suitably sized buffer at transfer->buffer.

Parameters:

transfer a transfer

Returns:: pointer to the first byte of the data section

static struct libusb_control_setup* libusb_control_transfer_get_setup ( struct libusb_transfer * transfer )

staticread

Get the control setup packet of a control transfer.

This convenience function is here to remind you that the control setup occupies the first 8 bytes of the transfer data buffer.

Calling this function only makes sense from a transfer callback function, or situations where you have already allocated a suitably sized buffer at transfer->buffer.

Parameters:

transfer a transfer

Returns:: a casted pointer to the start of the transfer data buffer

static void libusb_fill_control_setup	(	unsigned char *	buffer,
		uint8_t	bmRequestType,
		uint8_t	bRequest,
		uint16_t	wValue,
		uint16_t	wIndex,
		uint16_t	wLength
	)

inlinestatic

Helper function to populate the setup packet (first 8 bytes of the data buffer) for a control transfer.

The wIndex, wValue and wLength values should be given in host-endian byte order.

Parameters:

buffer	buffer to output the setup packet into
bmRequestType	see the bmRequestType field of libusb_control_setup
bRequest	see the bRequest field of libusb_control_setup
wValue	see the wValue field of libusb_control_setup
wIndex	see the wIndex field of libusb_control_setup
wLength	see the wLength field of libusb_control_setup

static void libusb_fill_control_transfer	(	struct libusb_transfer *	transfer,
		libusb_device_handle *	dev_handle,
		unsigned char *	buffer,
		libusb_transfer_cb_fn	callback,
		void *	user_data,
		unsigned int	timeout
	)

inlinestatic

Helper function to populate the required libusb_transfer fields for a control transfer.

If you pass a transfer buffer to this function, the first 8 bytes will be interpreted as a control setup packet, and the wLength field will be used to automatically populate the length field of the transfer. Therefore the recommended approach is:

Allocate a suitably sized data buffer (including space for control setup)
Call libusb_fill_control_setup()
If this is a host-to-device transfer with a data stage, put the data in place after the setup packet
Call this function
Call libusb_submit_transfer()

It is also legal to pass a NULL buffer to this function, in which case this function will not attempt to populate the length field. Remember that you must then populate the buffer and length fields later.

Parameters:

transfer	the transfer to populate
dev_handle	handle of the device that will handle the transfer
buffer	data buffer. If provided, this function will interpret the first 8 bytes as a setup packet and infer the transfer length from that.
callback	callback function to be invoked on transfer completion
user_data	user data to pass to callback function
timeout	timeout for the transfer in milliseconds

static void libusb_fill_bulk_transfer	(	struct libusb_transfer *	transfer,
		libusb_device_handle *	dev_handle,
		unsigned char	endpoint,
		unsigned char *	buffer,
		int	length,
		libusb_transfer_cb_fn	callback,
		void *	user_data,
		unsigned int	timeout
	)

inlinestatic

Helper function to populate the required libusb_transfer fields for a bulk transfer.

Parameters:

transfer	the transfer to populate
dev_handle	handle of the device that will handle the transfer
endpoint	address of the endpoint where this transfer will be sent
buffer	data buffer
length	length of data buffer
callback	callback function to be invoked on transfer completion
user_data	user data to pass to callback function
timeout	timeout for the transfer in milliseconds

static void libusb_fill_interrupt_transfer	(	struct libusb_transfer *	transfer,
		libusb_device_handle *	dev_handle,
		unsigned char	endpoint,
		unsigned char *	buffer,
		int	length,
		libusb_transfer_cb_fn	callback,
		void *	user_data,
		unsigned int	timeout
	)

inlinestatic

Helper function to populate the required libusb_transfer fields for an interrupt transfer.

Parameters:

transfer	the transfer to populate
dev_handle	handle of the device that will handle the transfer
endpoint	address of the endpoint where this transfer will be sent
buffer	data buffer
length	length of data buffer
callback	callback function to be invoked on transfer completion
user_data	user data to pass to callback function
timeout	timeout for the transfer in milliseconds

static void libusb_fill_iso_transfer	(	struct libusb_transfer *	transfer,
		libusb_device_handle *	dev_handle,
		unsigned char	endpoint,
		unsigned char *	buffer,
		int	length,
		int	num_iso_packets,
		libusb_transfer_cb_fn	callback,
		void *	user_data,
		unsigned int	timeout
	)

inlinestatic

Helper function to populate the required libusb_transfer fields for an isochronous transfer.

Parameters:

transfer	the transfer to populate
dev_handle	handle of the device that will handle the transfer
endpoint	address of the endpoint where this transfer will be sent
buffer	data buffer
length	length of data buffer
num_iso_packets	the number of isochronous packets
callback	callback function to be invoked on transfer completion
user_data	user data to pass to callback function
timeout	timeout for the transfer in milliseconds

static void libusb_set_iso_packet_lengths	(	struct libusb_transfer *	transfer,
		unsigned int	length
	)

inlinestatic

Convenience function to set the length of all packets in an isochronous transfer, based on the num_iso_packets field in the transfer structure.

Parameters:

transfer	a transfer
length	the length to set in each isochronous packet descriptor

See also:: libusb_get_max_packet_size()

static unsigned char* libusb_get_iso_packet_buffer	(	struct libusb_transfer *	transfer,
		unsigned int	packet
	)

inlinestatic

Convenience function to locate the position of an isochronous packet within the buffer of an isochronous transfer.

This is a thorough function which loops through all preceding packets, accumulating their lengths to find the position of the specified packet. Typically you will assign equal lengths to each packet in the transfer, and hence the above method is sub-optimal. You may wish to use libusb_get_iso_packet_buffer_simple() instead.

Parameters:

transfer	a transfer
packet	the packet to return the address of

Returns:: the base address of the packet buffer inside the transfer buffer, or NULL if the packet does not exist.

See also:: libusb_get_iso_packet_buffer_simple()

static unsigned char* libusb_get_iso_packet_buffer_simple	(	struct libusb_transfer *	transfer,
		unsigned int	packet
	)

inlinestatic

Convenience function to locate the position of an isochronous packet within the buffer of an isochronous transfer, for transfers where each packet is of identical size.

This function relies on the assumption that every packet within the transfer is of identical size to the first packet. Calculating the location of the packet buffer is then just a simple calculation: buffer + (packet_size * packet)

Do not use this function on transfers other than those that have identical packet lengths for each packet.

Parameters:

transfer	a transfer
packet	the packet to return the address of

Returns:: the base address of the packet buffer inside the transfer buffer, or NULL if the packet does not exist.

See also:: libusb_get_iso_packet_buffer()

Data Structures

Typedefs

Enumerations

Functions

Detailed Description

Transfer abstraction

Asynchronous transfers

Allocation

Filling

Submission

Completion handling

Deallocation

Resubmission

Cancellation

Overflows on device-to-host bulk/interrupt endpoints

Considerations for control transfers

Considerations for interrupt transfers

Considerations for isochronous transfers

Memory caveats

Fine control

Event handling

Typedef Documentation

Enumeration Type Documentation

Function Documentation