Lines Matching refs:OTG
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
32 API. This helps the OTG support, and looks forward to more-symmetric
151 OTG-capable systems will also need to include a standard Linux-USB host
153 (HCDs), *USB Device Drivers* to support the OTG "Targeted Peripheral
154 List", and so forth. There will also be an *OTG Controller Driver*,
157 new OTG protocols (HNP and SRP). Roles switch (host to peripheral, or
262 configurations, unless the hardware prevents such operation. For OTG
263 devices, each configuration descriptor includes an OTG descriptor.
271 allowed by that configuration. For OTG devices, setting a
296 Note that the lifecycle above can be slightly different for OTG devices.
297 Other than providing an additional OTG descriptor in each configuration,
447 USB On-The-GO (OTG)
450 USB OTG support on Linux 2.6 was initially developed by Texas
452 processors. Other OTG systems should work in similar ways, but the
455 Systems need specialized hardware support to implement OTG, notably
461 component (here called an "OTG Controller") affecting which driver stack
462 connects to the OTG port. In each role, the system can re-use the
466 support OTG can also benefit non-OTG products.
469 whether or not to include an OTG descriptor in each of their
472 - Gadget drivers may need changes to support the two new OTG protocols,
481 conserves battery power, which is useful even for non-OTG
484 - Also on the host side, a driver must support the OTG "Targeted
486 not supported with a given Linux OTG host. *This whitelist is
490 Non-OTG Linux hosts, like PCs and workstations, normally have some
503 Peripheral controller, and how the HCD initializes (since OTG can be
505 *OTG Controller Driver*, managing the OTG transceiver and the OTG state
506 machine logic as well as much of the root hub behavior for the OTG port.
507 The OTG controller driver needs to activate and deactivate USB
509 were needed inside usbcore, so that it can identify OTG-capable devices