|
struct | usb_hardware_func |
| Description of controller-specific data and functions. More...
|
|
struct | usbhc_func |
| pointers to kernel API functions that are called from *HCI-drivers More...
|
|
struct | usb_controller |
| Controller descriptor. This structure represents the common (controller-independent) part of a controller for the USB code. The corresponding controller-dependent part *hci_controller is located immediately before usb_controller. More...
|
|
struct | usb_pipe |
| Pipe descriptor. An USB pipe is described by two structures, for hardware and for software. This is the software part. The hardware part is defined in a driver of the corresponding controller. The hardware part is located immediately before usb_pipe, both are allocated at once by controller-specific code (it knows the total length, which depends on the hardware part). More...
|
|
struct | usb_static_ep |
| This structure describes the static head of every list of pipes. More...
|
|
struct | usb_gtd |
| This structure represents one transfer descriptor ('g' stands for "general" as opposed to isochronous usb_itd). Note that one transfer can have several descriptors: a control transfer has three stages. Additionally, every controller has a limit on transfer length with one descriptor (packet size for UHCI, 1K for OHCI, 4K for EHCI), large transfers must be split into individual packets according to that limit. More...
|
|
struct | usb_interface_data |
| Interface-specific data. Several interfaces of one device can operate independently, each is controlled by some driver and is identified by some driver-specific data passed as is to the driver. More...
|
|
struct | usb_device_data |
| Device-specific data. More...
|
|