2 # USB OTG infrastructure may be needed for peripheral-only, host-only,
3 # or OTG-capable configurations when OTG transceivers or controllers
7 comment "OTG and related infrastructure"
12 Select this to make sure the build includes objects from
13 the OTG infrastructure directory.
18 # USB Transceiver Drivers
21 tristate "GPIO based peripheral-only VBUS sensing 'transceiver'"
22 depends on GENERIC_GPIO
25 Provides simple GPIO VBUS sensing for controllers with an
26 internal transceiver via the otg_transceiver interface, and
27 optionally control of a D+ pullup GPIO as well as a VBUS
28 current limit regulator.
31 tristate "Philips ISP1301 with OMAP OTG"
32 depends on I2C && ARCH_OMAP_OTG
35 If you say yes here you get support for the Philips ISP1301
36 USB-On-The-Go transceiver working with the OMAP OTG controller.
37 The ISP1301 is a full speed USB transceiver which is used in
38 products including H2, H3, and H4 development boards for Texas
39 Instruments OMAP processors.
41 This driver can also be built as a module. If so, the module
42 will be called isp1301_omap.
45 bool "Generic ULPI Transceiver Driver"
49 Enable this to support ULPI connected USB OTG transceivers which
50 are likely found on embedded boards.
52 The only chip currently supported is NXP's ISP1504
55 tristate "TWL4030 USB Transceiver Driver"
56 depends on TWL4030_CORE && REGULATOR_TWL4030
59 Enable this to support the USB OTG transceiver on TWL4030
60 family chips (including the TWL5030 and TPS659x0 devices).
61 This transceiver supports high and full speed devices plus,
62 in host mode, low speed.
65 tristate "NOP USB Transceiver Driver"
68 this driver is to be used by all the usb transceiver which are either
69 built-in with usb ip or which are autonomous and doesn't require any
70 phy programming such as ISP1x04 etc.