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 usb_phy 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 config USB_ULPI_VIEWPORT
56 Provides read/write operations to the ULPI phy register set for
57 controllers with a viewport register (e.g. Chipidea/ARC controllers).
60 tristate "TWL4030 USB Transceiver Driver"
61 depends on TWL4030_CORE && REGULATOR_TWL4030
64 Enable this to support the USB OTG transceiver on TWL4030
65 family chips (including the TWL5030 and TPS659x0 devices).
66 This transceiver supports high and full speed devices plus,
67 in host mode, low speed.
70 tristate "TWL6030 USB Transceiver Driver"
71 depends on TWL4030_CORE && OMAP_USB2
74 Enable this to support the USB OTG transceiver on TWL6030
75 family chips. This TWL6030 transceiver has the VBUS and ID GND
76 and OTG SRP events capabilities. For all other transceiver functionality
77 UTMI PHY is embedded in OMAP4430. The internal PHY configurations APIs
78 are hooked to this driver through platform_data structure.
79 The definition of internal PHY APIs are in the mach-omap2 layer.
82 tristate "NOP USB Transceiver Driver"
85 This driver is to be used by all the usb transceiver which are either
86 built-in with usb ip or which are autonomous and doesn't require any
87 phy programming such as ISP1x04 etc.
90 tristate "OTG support for Qualcomm on-chip USB controller"
91 depends on (USB || USB_GADGET) && ARCH_MSM
94 Enable this to support the USB OTG transceiver on MSM chips. It
95 handles PHY initialization, clock management, and workarounds
96 required after resetting the hardware and power management.
97 This driver is required even for peripheral only or host only
99 This driver is not supported on boards like trout which
103 tristate "AB8500 USB Transceiver Driver"
104 depends on AB8500_CORE
107 Enable this to support the USB OTG transceiver in AB8500 chip.
108 This transceiver supports high and full speed devices plus,
109 in host mode, low speed.
112 bool "Freescale USB OTG Transceiver Driver"
113 depends on USB_EHCI_FSL && USB_GADGET_FSL_USB2 && USB_SUSPEND
117 Enable this to support Freescale USB OTG transceiver.
120 tristate "Freescale MXS USB PHY support"
121 depends on ARCH_MXC || ARCH_MXS
125 Enable this to support the Freescale MXS USB PHY.
127 MXS Phy is used by some of the i.MX SoCs, for example imx23/28/6x.
130 tristate "Marvell USB OTG support"
131 depends on USB_EHCI_MV && USB_MV_UDC && USB_SUSPEND
135 Say Y here if you want to build Marvell USB OTG transciever
136 driver in kernel (including PXA and MMP series). This driver
137 implements role switch between EHCI host driver and gadget driver.
139 To compile this driver as a module, choose M here.