Lines Matching +full:event +full:- +full:touch +full:- +full:alt
1 .. _usb-hostside-api:
4 The Linux-USB Host Side API
18 That master/slave asymmetry was designed-in for a number of reasons, one
22 distributed auto-configuration since the pre-designated master node
37 USB Host-Side API Model
40 Host-side drivers for USB devices talk to the "usbcore" APIs. There are
41 two. One is intended for *general-purpose* drivers (exposed through
49 - USB supports four kinds of data transfers (control, bulk, interrupt,
54 - The device description model includes one or more "configurations"
60 - From USB 3.0 on configurations have one or more "functions", which
64 - Configurations or functions have one or more "interfaces", each of which may have
74 - Interfaces have one or more "endpoints", each of which supports one
79 - Data transfer on USB is packetized; each endpoint has a maximum
84 - The Linux USB API supports synchronous calls for control and bulk
94 The only host-side drivers that actually touch hardware (reading/writing
101 faults (including software-induced ones like unlinking an URB) isn't yet
105 well as to make sure they aren't relying on some HCD-specific behavior.
109 USB-Standard Types
117 .. kernel-doc:: include/linux/usb/ch9.h
122 Host-Side Data Types and Macros
130 .. kernel-doc:: include/linux/usb.h
142 per-packet fault reports). Built on top of that is synchronous API
145 wrappers for single-buffer control and bulk transfers (which are awkward
155 .. kernel-doc:: drivers/usb/core/urb.c
158 .. kernel-doc:: drivers/usb/core/message.c
161 .. kernel-doc:: drivers/usb/core/file.c
164 .. kernel-doc:: drivers/usb/core/driver.c
167 .. kernel-doc:: drivers/usb/core/usb.c
170 .. kernel-doc:: drivers/usb/core/hub.c
187 based controllers (and a few non-PCI based ones) use one of those
197 significantly reduce hcd-specific behaviors.
199 .. kernel-doc:: drivers/usb/core/hcd.c
202 .. kernel-doc:: drivers/usb/core/hcd-pci.c
205 .. kernel-doc:: drivers/usb/core/buffer.c
217 - `libusb <http://libusb.sourceforge.net>`__ for C/C++, and
218 - `jUSB <http://jUSB.sourceforge.net>`__ for Java.
222 at http://www.linux-usb.org/
226 - They were used to be implemented via *usbfs*, but this is not part of
229 - This particular documentation is incomplete, especially with respect
231 (new) documentation need to be cross-reviewed.
234 -----------------------------
238 - ``/dev/bus/usb/BBB/DDD`` ... magic files exposing the each device's
254 --------------------
258 - *They can be read,* producing first the device descriptor (18 bytes) and
263 the BCD-encoded fields, and the vendor and product IDs) will be
268 - *Perform USB operations* using *ioctl()* requests to make endpoint I/O
282 it's relatively common for devices to re-enumerate while they are
289 configuration of the device. Multi-byte fields in the device descriptor
297 These files may also be used to write user-level drivers for the USB
314 -------------------------------
318 event handling agent chose that driver to handle the new device. Or
333 (An example might be software using vendor-specific control requests for
337 More likely, you need a more complex style driver: one using non-control
346 Your user-mode driver should never need to worry about cleaning up
351 --------------------
368 :ref:`usb-error-codes`).
373 hub_wq (in the kernel) setting a device-wide *configuration* that
440 * 'request' becomes the driver->ioctl() 'code' parameter.
442 * is copied to or from the driver->ioctl() 'buf' parameter.
461 devices what device special file should be used. Two pre-defined
537 returning ``-EPIPE`` status to a data transfer request. Do not issue
624 (It's usually a pointer to per-request data.) Flags can modify requests
683 - ``/sys/kernel/debug/usb/devices`` ... a text file showing each of the USB
688 -----------------------------
692 (including class and vendor status) is available from device-specific
705 poll(&pfd, 1, -1);
713 udev or HAL to initialize a device or start a user-mode helper program,
724 Each line is tagged with a one-character ID for that line::
868 rather differently. For example, a bus-powered configuration
869 might be much less capable than one that is self-powered. Only
883 I:* If#=dd Alt=dd #EPs=dd Cls=xx(sssss) Sub=xx Prot=xx Driver=ssss
898 of bus bandwidth, drivers must select a non-default altsetting.
922 the per-microframe data transfer size. For "high bandwidth"
926 With the Linux-USB stack, periodic bandwidth reservations use the
936 ``grep -i ^[tdp]: /sys/kernel/debug/usb/devices`` can be used to list
970 I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
977 I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
984 I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=mouse
993 I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=serial
1006 I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
1008 I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=mouse
1010 I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=serial
1015 +------------------+
1017 +------------------+ (nn) is Mbps.
1019 +------------------+
1022 +-----------------------+
1023 Level 1 | Dev#2: 4-port hub (12)|
1024 +-----------------------+
1026 +-----------------------+
1030 +--------------------+ +--------------------+
1032 +--------------------+ +--------------------+
1036 Or, in a more tree-like structure (ports [Connectors] without