1# 2# Physical Layer USB driver configuration 3# 4menuconfig USB_PHY 5 bool "USB Physical Layer drivers" 6 help 7 Most USB controllers have the physical layer signalling part 8 (commonly called a PHY) built in. However, dual-role devices 9 (a.k.a. USB on-the-go) which support being USB master or slave 10 with the same connector often use an external PHY. 11 12 The drivers in this submenu add support for such PHY devices. 13 They are not needed for standard master-only (or the vast 14 majority of slave-only) USB interfaces. 15 16 If you're not sure if this applies to you, it probably doesn't; 17 say N here. 18 19config USB_OTG_WAKELOCK 20 bool "Hold a wakelock when USB connected" 21 depends on WAKELOCK 22 select USB_OTG_UTILS 23 help 24 Select this to automatically hold a wakelock when USB is 25 connected, preventing suspend. 26 27if USB_PHY 28 29# 30# USB Transceiver Drivers 31# 32config AB8500_USB 33 tristate "AB8500 USB Transceiver Driver" 34 depends on AB8500_CORE 35 help 36 Enable this to support the USB OTG transceiver in AB8500 chip. 37 This transceiver supports high and full speed devices plus, 38 in host mode, low speed. 39 40config FSL_USB2_OTG 41 bool "Freescale USB OTG Transceiver Driver" 42 depends on USB_EHCI_FSL && USB_FSL_USB2 && PM_RUNTIME 43 select USB_OTG 44 help 45 Enable this to support Freescale USB OTG transceiver. 46 47config ISP1301_OMAP 48 tristate "Philips ISP1301 with OMAP OTG" 49 depends on I2C && ARCH_OMAP_OTG 50 help 51 If you say yes here you get support for the Philips ISP1301 52 USB-On-The-Go transceiver working with the OMAP OTG controller. 53 The ISP1301 is a full speed USB transceiver which is used in 54 products including H2, H3, and H4 development boards for Texas 55 Instruments OMAP processors. 56 57 This driver can also be built as a module. If so, the module 58 will be called isp1301_omap. 59 60config MV_U3D_PHY 61 bool "Marvell USB 3.0 PHY controller Driver" 62 depends on CPU_MMP3 63 help 64 Enable this to support Marvell USB 3.0 phy controller for Marvell 65 SoC. 66 67config NOP_USB_XCEIV 68 tristate "NOP USB Transceiver Driver" 69 help 70 This driver is to be used by all the usb transceiver which are either 71 built-in with usb ip or which are autonomous and doesn't require any 72 phy programming such as ISP1x04 etc. 73 74config OMAP_CONTROL_USB 75 tristate "OMAP CONTROL USB Driver" 76 help 77 Enable this to add support for the USB part present in the control 78 module. This driver has API to power on the USB2 PHY and to write to 79 the mailbox. The mailbox is present only in omap4 and the register to 80 power on the USB2 PHY is present in OMAP4 and OMAP5. OMAP5 has an 81 additional register to power on USB3 PHY. 82 83config OMAP_USB2 84 tristate "OMAP USB2 PHY Driver" 85 depends on ARCH_OMAP2PLUS 86 select OMAP_CONTROL_USB 87 help 88 Enable this to support the transceiver that is part of SOC. This 89 driver takes care of all the PHY functionality apart from comparator. 90 The USB OTG controller communicates with the comparator using this 91 driver. 92 93config OMAP_USB3 94 tristate "OMAP USB3 PHY Driver" 95 select OMAP_CONTROL_USB 96 help 97 Enable this to support the USB3 PHY that is part of SOC. This 98 driver takes care of all the PHY functionality apart from comparator. 99 This driver interacts with the "OMAP Control USB Driver" to power 100 on/off the PHY. 101 102config SAMSUNG_USBPHY 103 tristate "Samsung USB PHY Driver" 104 help 105 Enable this to support Samsung USB phy helper driver for Samsung SoCs. 106 This driver provides common interface to interact, for Samsung USB 2.0 PHY 107 driver and later for Samsung USB 3.0 PHY driver. 108 109config SAMSUNG_USB2PHY 110 tristate "Samsung USB 2.0 PHY controller Driver" 111 select SAMSUNG_USBPHY 112 help 113 Enable this to support Samsung USB 2.0 (High Speed) PHY controller 114 driver for Samsung SoCs. 115 116config SAMSUNG_USB3PHY 117 tristate "Samsung USB 3.0 PHY controller Driver" 118 select SAMSUNG_USBPHY 119 help 120 Enable this to support Samsung USB 3.0 (Super Speed) phy controller 121 for samsung SoCs. 122 123config TWL4030_USB 124 tristate "TWL4030 USB Transceiver Driver" 125 depends on TWL4030_CORE && REGULATOR_TWL4030 && USB_MUSB_OMAP2PLUS 126 help 127 Enable this to support the USB OTG transceiver on TWL4030 128 family chips (including the TWL5030 and TPS659x0 devices). 129 This transceiver supports high and full speed devices plus, 130 in host mode, low speed. 131 132config TWL6030_USB 133 tristate "TWL6030 USB Transceiver Driver" 134 depends on TWL4030_CORE && OMAP_USB2 && USB_MUSB_OMAP2PLUS 135 help 136 Enable this to support the USB OTG transceiver on TWL6030 137 family chips. This TWL6030 transceiver has the VBUS and ID GND 138 and OTG SRP events capabilities. For all other transceiver functionality 139 UTMI PHY is embedded in OMAP4430. The internal PHY configurations APIs 140 are hooked to this driver through platform_data structure. 141 The definition of internal PHY APIs are in the mach-omap2 layer. 142 143config USB_GPIO_VBUS 144 tristate "GPIO based peripheral-only VBUS sensing 'transceiver'" 145 depends on GPIOLIB 146 help 147 Provides simple GPIO VBUS sensing for controllers with an 148 internal transceiver via the usb_phy interface, and 149 optionally control of a D+ pullup GPIO as well as a VBUS 150 current limit regulator. 151 152config USB_ISP1301 153 tristate "NXP ISP1301 USB transceiver support" 154 depends on USB || USB_GADGET 155 depends on I2C 156 help 157 Say Y here to add support for the NXP ISP1301 USB transceiver driver. 158 This chip is typically used as USB transceiver for USB host, gadget 159 and OTG drivers (to be selected separately). 160 161 To compile this driver as a module, choose M here: the 162 module will be called isp1301. 163 164config USB_MSM_OTG 165 tristate "OTG support for Qualcomm on-chip USB controller" 166 depends on (USB || USB_GADGET) && ARCH_MSM 167 help 168 Enable this to support the USB OTG transceiver on MSM chips. It 169 handles PHY initialization, clock management, and workarounds 170 required after resetting the hardware and power management. 171 This driver is required even for peripheral only or host only 172 mode configurations. 173 This driver is not supported on boards like trout which 174 has an external PHY. 175 176config USB_MV_OTG 177 tristate "Marvell USB OTG support" 178 depends on USB_EHCI_MV && USB_MV_UDC && PM_RUNTIME 179 select USB_OTG 180 help 181 Say Y here if you want to build Marvell USB OTG transciever 182 driver in kernel (including PXA and MMP series). This driver 183 implements role switch between EHCI host driver and gadget driver. 184 185 To compile this driver as a module, choose M here. 186 187config USB_MXS_PHY 188 tristate "Freescale MXS USB PHY support" 189 depends on ARCH_MXC || ARCH_MXS 190 select STMP_DEVICE 191 help 192 Enable this to support the Freescale MXS USB PHY. 193 194 MXS Phy is used by some of the i.MX SoCs, for example imx23/28/6x. 195 196config USB_RCAR_PHY 197 tristate "Renesas R-Car USB phy support" 198 depends on USB || USB_GADGET 199 help 200 Say Y here to add support for the Renesas R-Car USB phy driver. 201 This chip is typically used as USB phy for USB host, gadget. 202 This driver supports: R8A7779 203 204 To compile this driver as a module, choose M here: the 205 module will be called rcar-phy. 206 207config USB_ULPI 208 bool "Generic ULPI Transceiver Driver" 209 depends on ARM 210 help 211 Enable this to support ULPI connected USB OTG transceivers which 212 are likely found on embedded boards. 213 214config USB_ULPI_VIEWPORT 215 bool 216 depends on USB_ULPI 217 help 218 Provides read/write operations to the ULPI phy register set for 219 controllers with a viewport register (e.g. Chipidea/ARC controllers). 220 221config DUAL_ROLE_USB_INTF 222 bool "Generic DUAL ROLE sysfs interface" 223 depends on SYSFS && USB_PHY 224 help 225 A generic sysfs interface to track and change the state of 226 dual role usb phys. The usb phy drivers can register to 227 this interface to expose it capabilities to the userspace 228 and thereby allowing userspace to change the port mode. 229 230endif # USB_PHY 231