2 # Physical Layer USB driver configuration
5 bool "USB Physical Layer drivers"
7 USB controllers (those which are host, device or DRD) need a
8 device to handle the physical layer signalling, commonly called
11 The following drivers add support for such PHY devices.
16 # USB Transceiver Drivers
19 tristate "AB8500 USB Transceiver Driver"
20 depends on AB8500_CORE
22 Enable this to support the USB OTG transceiver in AB8500 chip.
23 This transceiver supports high and full speed devices plus,
24 in host mode, low speed.
27 bool "Freescale USB OTG Transceiver Driver"
28 depends on USB_EHCI_FSL && USB_FSL_USB2 && PM_RUNTIME
31 Enable this to support Freescale USB OTG transceiver.
34 tristate "Philips ISP1301 with OMAP OTG"
35 depends on I2C && ARCH_OMAP_OTG
37 If you say yes here you get support for the Philips ISP1301
38 USB-On-The-Go transceiver working with the OMAP OTG controller.
39 The ISP1301 is a full speed USB transceiver which is used in
40 products including H2, H3, and H4 development boards for Texas
41 Instruments OMAP processors.
43 This driver can also be built as a module. If so, the module
44 will be called isp1301_omap.
47 bool "Marvell USB 3.0 PHY controller Driver"
50 Enable this to support Marvell USB 3.0 phy controller for Marvell
54 tristate "NOP USB Transceiver Driver"
56 This driver is to be used by all the usb transceiver which are either
57 built-in with usb ip or which are autonomous and doesn't require any
58 phy programming such as ISP1x04 etc.
60 config OMAP_CONTROL_USB
61 tristate "OMAP CONTROL USB Driver"
63 Enable this to add support for the USB part present in the control
64 module. This driver has API to power on the USB2 PHY and to write to
65 the mailbox. The mailbox is present only in omap4 and the register to
66 power on the USB2 PHY is present in OMAP4 and OMAP5. OMAP5 has an
67 additional register to power on USB3 PHY.
70 tristate "OMAP USB2 PHY Driver"
71 depends on ARCH_OMAP2PLUS
72 select OMAP_CONTROL_USB
74 Enable this to support the transceiver that is part of SOC. This
75 driver takes care of all the PHY functionality apart from comparator.
76 The USB OTG controller communicates with the comparator using this
80 tristate "OMAP USB3 PHY Driver"
81 select OMAP_CONTROL_USB
83 Enable this to support the USB3 PHY that is part of SOC. This
84 driver takes care of all the PHY functionality apart from comparator.
85 This driver interacts with the "OMAP Control USB Driver" to power
89 tristate "Samsung USB PHY Driver"
91 Enable this to support Samsung USB phy helper driver for Samsung SoCs.
92 This driver provides common interface to interact, for Samsung USB 2.0 PHY
93 driver and later for Samsung USB 3.0 PHY driver.
95 config SAMSUNG_USB2PHY
96 tristate "Samsung USB 2.0 PHY controller Driver"
99 Enable this to support Samsung USB 2.0 (High Speed) PHY controller
100 driver for Samsung SoCs.
102 config SAMSUNG_USB3PHY
103 tristate "Samsung USB 3.0 PHY controller Driver"
104 select SAMSUNG_USBPHY
106 Enable this to support Samsung USB 3.0 (Super Speed) phy controller
110 tristate "TWL4030 USB Transceiver Driver"
111 depends on TWL4030_CORE && REGULATOR_TWL4030 && USB_MUSB_OMAP2PLUS
113 Enable this to support the USB OTG transceiver on TWL4030
114 family chips (including the TWL5030 and TPS659x0 devices).
115 This transceiver supports high and full speed devices plus,
116 in host mode, low speed.
119 tristate "TWL6030 USB Transceiver Driver"
120 depends on TWL4030_CORE && OMAP_USB2 && USB_MUSB_OMAP2PLUS
122 Enable this to support the USB OTG transceiver on TWL6030
123 family chips. This TWL6030 transceiver has the VBUS and ID GND
124 and OTG SRP events capabilities. For all other transceiver functionality
125 UTMI PHY is embedded in OMAP4430. The internal PHY configurations APIs
126 are hooked to this driver through platform_data structure.
127 The definition of internal PHY APIs are in the mach-omap2 layer.
130 tristate "GPIO based peripheral-only VBUS sensing 'transceiver'"
133 Provides simple GPIO VBUS sensing for controllers with an
134 internal transceiver via the usb_phy interface, and
135 optionally control of a D+ pullup GPIO as well as a VBUS
136 current limit regulator.
139 tristate "NXP ISP1301 USB transceiver support"
140 depends on USB || USB_GADGET
143 Say Y here to add support for the NXP ISP1301 USB transceiver driver.
144 This chip is typically used as USB transceiver for USB host, gadget
145 and OTG drivers (to be selected separately).
147 To compile this driver as a module, choose M here: the
148 module will be called isp1301.
151 tristate "OTG support for Qualcomm on-chip USB controller"
152 depends on (USB || USB_GADGET) && ARCH_MSM
154 Enable this to support the USB OTG transceiver on MSM chips. It
155 handles PHY initialization, clock management, and workarounds
156 required after resetting the hardware and power management.
157 This driver is required even for peripheral only or host only
159 This driver is not supported on boards like trout which
163 tristate "Marvell USB OTG support"
164 depends on USB_EHCI_MV && USB_MV_UDC && PM_RUNTIME
167 Say Y here if you want to build Marvell USB OTG transciever
168 driver in kernel (including PXA and MMP series). This driver
169 implements role switch between EHCI host driver and gadget driver.
171 To compile this driver as a module, choose M here.
174 tristate "Freescale MXS USB PHY support"
175 depends on ARCH_MXC || ARCH_MXS
178 Enable this to support the Freescale MXS USB PHY.
180 MXS Phy is used by some of the i.MX SoCs, for example imx23/28/6x.
183 tristate "Renesas R-Car USB phy support"
184 depends on USB || USB_GADGET
186 Say Y here to add support for the Renesas R-Car USB phy driver.
187 This chip is typically used as USB phy for USB host, gadget.
188 This driver supports: R8A7779
190 To compile this driver as a module, choose M here: the
191 module will be called rcar-phy.
194 bool "Generic ULPI Transceiver Driver"
197 Enable this to support ULPI connected USB OTG transceivers which
198 are likely found on embedded boards.
200 config USB_ULPI_VIEWPORT
204 Provides read/write operations to the ULPI phy register set for
205 controllers with a viewport register (e.g. Chipidea/ARC controllers).