Lines Matching full:drivers

21    just two fixed-function ones. Gadget drivers can be written so
34    side drivers).
43 distinguish drivers running inside such hardware from the more familiar
44 Linux "USB device drivers", which are host side proxies for the real USB
45 devices, a different term is used: the drivers inside the peripherals
46 are "USB gadget drivers". In USB protocol interactions, the device
54 bind and unbind drivers to devices. The APIs differ in detail, since the
62 Structure of Gadget Drivers
79     callbacks that interact with gadget drivers. Since normal USB
81     drivers. The controller driver can support any number of different
82     gadget drivers, but only one of them can be used at a time.
94     supported by one particular controller. Gadget drivers may be
98     automatically for many bulk-oriented drivers.) Gadget driver
115     Such drivers may be modules of proprietary code, although that
119     Most gadget drivers have an upper boundary that connects to some
130     -  data capture drivers, perhaps video4Linux or a scanner driver; or
152 side stack, with ``usbcore``, one or more *Host Controller Drivers*
153 (HCDs), *USB Device Drivers* to support the OTG "Targeted Peripheral
164 endpoints is now automated, and many drivers now use autoconfiguration
171 NFS are. Such gadget-side interface drivers should eventually be
177 Gadget drivers declare themselves through a struct
209 This API allows drivers to use conditional compilation to handle
216 Many drivers will be able to at least partially autoconfigure
225 packet boundaries are visible to drivers. Compared to RS-232 serial
230 drivers won't buffer two single byte writes into a single two-byte USB
231 IN packet, although gadget drivers may do so when they implement
238 Gadget drivers make endpoint I/O requests to hardware without needing to
279    times before being disconnected. On disconnect, the drivers go back
285 Drivers will normally be arranged so that just loading the gadget driver
287 peripheral device to be enumerated, but some drivers will defer
291 USB specifications. Such issues are in the domain of gadget drivers,
306 Gadget drivers rely on common USB structures and constants defined in
309 drivers (and usbcore).
315 drivers to interact with USB peripheral controller drivers.
327 .. kernel-doc:: drivers/usb/gadget/usbstring.c
330 .. kernel-doc:: drivers/usb/gadget/config.c
336 The core API is sufficient for writing drivers for composite USB devices
352 .. kernel-doc:: drivers/usb/gadget/composite.c
358 At this writing, a few of the current gadget drivers have been converted
362 Peripheral Controller Drivers
378 At this writing, there are people at work on drivers in this framework
396 Gadget Drivers
400 with drivers for usb controller hardware), other gadget drivers exist.
418 versions of Windows, using drivers that Microsoft bundles and supports,
421 There is also support for user mode gadget drivers, using ``gadgetfs``.
425 user mode drivers, so that once a robust controller driver is available
463 existing pool of hardware-neutral drivers, layered on top of the
465 Such drivers need at most minor changes, and most of the calls added to
468 -  Gadget drivers test the ``is_otg`` flag, and use it to determine
472 -  Gadget drivers may need changes to support the two new OTG protocols,
479 -  On the host side, USB device drivers need to be taught to trigger HNP
491    solution for adding drivers, so that peripherals that aren't