Kconfig 6.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200
  1. #
  2. # Physical Layer USB driver configuration
  3. #
  4. menuconfig USB_PHY
  5. tristate "USB Physical Layer drivers"
  6. help
  7. USB controllers (those which are host, device or DRD) need a
  8. device to handle the physical layer signalling, commonly called
  9. a PHY.
  10. The following drivers add support for such PHY devices.
  11. if USB_PHY
  12. #
  13. # USB Transceiver Drivers
  14. #
  15. config AB8500_USB
  16. tristate "AB8500 USB Transceiver Driver"
  17. depends on AB8500_CORE
  18. help
  19. Enable this to support the USB OTG transceiver in AB8500 chip.
  20. This transceiver supports high and full speed devices plus,
  21. in host mode, low speed.
  22. config FSL_USB2_OTG
  23. bool "Freescale USB OTG Transceiver Driver"
  24. depends on USB_EHCI_FSL && USB_FSL_USB2 && USB_SUSPEND
  25. select USB_OTG
  26. help
  27. Enable this to support Freescale USB OTG transceiver.
  28. config ISP1301_OMAP
  29. tristate "Philips ISP1301 with OMAP OTG"
  30. depends on I2C && ARCH_OMAP_OTG
  31. help
  32. If you say yes here you get support for the Philips ISP1301
  33. USB-On-The-Go transceiver working with the OMAP OTG controller.
  34. The ISP1301 is a full speed USB transceiver which is used in
  35. products including H2, H3, and H4 development boards for Texas
  36. Instruments OMAP processors.
  37. This driver can also be built as a module. If so, the module
  38. will be called isp1301_omap.
  39. config MV_U3D_PHY
  40. bool "Marvell USB 3.0 PHY controller Driver"
  41. depends on USB_MV_U3D
  42. help
  43. Enable this to support Marvell USB 3.0 phy controller for Marvell
  44. SoC.
  45. config NOP_USB_XCEIV
  46. tristate "NOP USB Transceiver Driver"
  47. help
  48. This driver is to be used by all the usb transceiver which are either
  49. built-in with usb ip or which are autonomous and doesn't require any
  50. phy programming such as ISP1x04 etc.
  51. config OMAP_CONTROL_USB
  52. tristate "OMAP CONTROL USB Driver"
  53. help
  54. Enable this to add support for the USB part present in the control
  55. module. This driver has API to power on the USB2 PHY and to write to
  56. the mailbox. The mailbox is present only in omap4 and the register to
  57. power on the USB2 PHY is present in OMAP4 and OMAP5. OMAP5 has an
  58. additional register to power on USB3 PHY.
  59. config OMAP_USB2
  60. tristate "OMAP USB2 PHY Driver"
  61. depends on ARCH_OMAP2PLUS
  62. select OMAP_CONTROL_USB
  63. help
  64. Enable this to support the transceiver that is part of SOC. This
  65. driver takes care of all the PHY functionality apart from comparator.
  66. The USB OTG controller communicates with the comparator using this
  67. driver.
  68. config OMAP_USB3
  69. tristate "OMAP USB3 PHY Driver"
  70. select OMAP_CONTROL_USB
  71. help
  72. Enable this to support the USB3 PHY that is part of SOC. This
  73. driver takes care of all the PHY functionality apart from comparator.
  74. This driver interacts with the "OMAP Control USB Driver" to power
  75. on/off the PHY.
  76. config SAMSUNG_USBPHY
  77. tristate "Samsung USB PHY Driver"
  78. help
  79. Enable this to support Samsung USB phy helper driver for Samsung SoCs.
  80. This driver provides common interface to interact, for Samsung USB 2.0 PHY
  81. driver and later for Samsung USB 3.0 PHY driver.
  82. config SAMSUNG_USB2PHY
  83. tristate "Samsung USB 2.0 PHY controller Driver"
  84. select SAMSUNG_USBPHY
  85. help
  86. Enable this to support Samsung USB 2.0 (High Speed) PHY controller
  87. driver for Samsung SoCs.
  88. config TWL4030_USB
  89. tristate "TWL4030 USB Transceiver Driver"
  90. depends on TWL4030_CORE && REGULATOR_TWL4030 && USB_MUSB_OMAP2PLUS
  91. help
  92. Enable this to support the USB OTG transceiver on TWL4030
  93. family chips (including the TWL5030 and TPS659x0 devices).
  94. This transceiver supports high and full speed devices plus,
  95. in host mode, low speed.
  96. config TWL6030_USB
  97. tristate "TWL6030 USB Transceiver Driver"
  98. depends on TWL4030_CORE && OMAP_USB2 && USB_MUSB_OMAP2PLUS
  99. help
  100. Enable this to support the USB OTG transceiver on TWL6030
  101. family chips. This TWL6030 transceiver has the VBUS and ID GND
  102. and OTG SRP events capabilities. For all other transceiver functionality
  103. UTMI PHY is embedded in OMAP4430. The internal PHY configurations APIs
  104. are hooked to this driver through platform_data structure.
  105. The definition of internal PHY APIs are in the mach-omap2 layer.
  106. config USB_GPIO_VBUS
  107. tristate "GPIO based peripheral-only VBUS sensing 'transceiver'"
  108. depends on GENERIC_GPIO
  109. help
  110. Provides simple GPIO VBUS sensing for controllers with an
  111. internal transceiver via the usb_phy interface, and
  112. optionally control of a D+ pullup GPIO as well as a VBUS
  113. current limit regulator.
  114. config USB_ISP1301
  115. tristate "NXP ISP1301 USB transceiver support"
  116. depends on USB || USB_GADGET
  117. depends on I2C
  118. help
  119. Say Y here to add support for the NXP ISP1301 USB transceiver driver.
  120. This chip is typically used as USB transceiver for USB host, gadget
  121. and OTG drivers (to be selected separately).
  122. To compile this driver as a module, choose M here: the
  123. module will be called isp1301.
  124. config USB_MSM_OTG
  125. tristate "OTG support for Qualcomm on-chip USB controller"
  126. depends on (USB || USB_GADGET) && ARCH_MSM
  127. help
  128. Enable this to support the USB OTG transceiver on MSM chips. It
  129. handles PHY initialization, clock management, and workarounds
  130. required after resetting the hardware and power management.
  131. This driver is required even for peripheral only or host only
  132. mode configurations.
  133. This driver is not supported on boards like trout which
  134. has an external PHY.
  135. config USB_MV_OTG
  136. tristate "Marvell USB OTG support"
  137. depends on USB_EHCI_MV && USB_MV_UDC && USB_SUSPEND
  138. select USB_OTG
  139. help
  140. Say Y here if you want to build Marvell USB OTG transciever
  141. driver in kernel (including PXA and MMP series). This driver
  142. implements role switch between EHCI host driver and gadget driver.
  143. To compile this driver as a module, choose M here.
  144. config USB_MXS_PHY
  145. tristate "Freescale MXS USB PHY support"
  146. depends on ARCH_MXC || ARCH_MXS
  147. select STMP_DEVICE
  148. help
  149. Enable this to support the Freescale MXS USB PHY.
  150. MXS Phy is used by some of the i.MX SoCs, for example imx23/28/6x.
  151. config USB_RCAR_PHY
  152. tristate "Renesas R-Car USB phy support"
  153. depends on USB || USB_GADGET
  154. help
  155. Say Y here to add support for the Renesas R-Car USB phy driver.
  156. This chip is typically used as USB phy for USB host, gadget.
  157. This driver supports: R8A7779
  158. To compile this driver as a module, choose M here: the
  159. module will be called rcar-phy.
  160. config USB_ULPI
  161. bool "Generic ULPI Transceiver Driver"
  162. depends on ARM
  163. help
  164. Enable this to support ULPI connected USB OTG transceivers which
  165. are likely found on embedded boards.
  166. config USB_ULPI_VIEWPORT
  167. bool
  168. depends on USB_ULPI
  169. help
  170. Provides read/write operations to the ULPI phy register set for
  171. controllers with a viewport register (e.g. Chipidea/ARC controllers).
  172. endif # USB_PHY