Kconfig 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405
  1. #
  2. # USB Gadget support on a system involves
  3. # (a) a peripheral controller, and
  4. # (b) the gadget driver using it.
  5. #
  6. # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
  7. #
  8. # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
  9. # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
  10. # - Some systems have both kinds of controllers.
  11. #
  12. # With help from a special transceiver and a "Mini-AB" jack, systems with
  13. # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
  14. #
  15. #
  16. # USB Peripheral Controller Support
  17. #
  18. # The order here is alphabetical, except that integrated controllers go
  19. # before discrete ones so they will be the initial/default value:
  20. # - integrated/SOC controllers first
  21. # - licensed IP used in both SOC and discrete versions
  22. # - discrete ones (including all PCI-only controllers)
  23. # - debug/dummy gadget+hcd is last.
  24. #
  25. menu "USB Peripheral Controller"
  26. #
  27. # Integrated controllers
  28. #
  29. config USB_AT91
  30. tristate "Atmel AT91 USB Device Port"
  31. depends on ARCH_AT91
  32. depends on OF || COMPILE_TEST
  33. help
  34. Many Atmel AT91 processors (such as the AT91RM2000) have a
  35. full speed USB Device Port with support for five configurable
  36. endpoints (plus endpoint zero).
  37. Say "y" to link the driver statically, or "m" to build a
  38. dynamically linked module called "at91_udc" and force all
  39. gadget drivers to also be dynamically linked.
  40. config USB_LPC32XX
  41. tristate "LPC32XX USB Peripheral Controller"
  42. depends on ARCH_LPC32XX && I2C
  43. select USB_ISP1301
  44. help
  45. This option selects the USB device controller in the LPC32xx SoC.
  46. Say "y" to link the driver statically, or "m" to build a
  47. dynamically linked module called "lpc32xx_udc" and force all
  48. gadget drivers to also be dynamically linked.
  49. config USB_ATMEL_USBA
  50. tristate "Atmel USBA"
  51. depends on ((AVR32 && !OF) || ARCH_AT91)
  52. help
  53. USBA is the integrated high-speed USB Device controller on
  54. the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
  55. config USB_BCM63XX_UDC
  56. tristate "Broadcom BCM63xx Peripheral Controller"
  57. depends on BCM63XX
  58. help
  59. Many Broadcom BCM63xx chipsets (such as the BCM6328) have a
  60. high speed USB Device Port with support for four fixed endpoints
  61. (plus endpoint zero).
  62. Say "y" to link the driver statically, or "m" to build a
  63. dynamically linked module called "bcm63xx_udc".
  64. config USB_FSL_USB2
  65. tristate "Freescale Highspeed USB DR Peripheral Controller"
  66. depends on FSL_SOC || ARCH_MXC
  67. select USB_FSL_MPH_DR_OF if OF
  68. help
  69. Some of Freescale PowerPC and i.MX processors have a High Speed
  70. Dual-Role(DR) USB controller, which supports device mode.
  71. The number of programmable endpoints is different through
  72. SOC revisions.
  73. Say "y" to link the driver statically, or "m" to build a
  74. dynamically linked module called "fsl_usb2_udc" and force
  75. all gadget drivers to also be dynamically linked.
  76. config USB_FUSB300
  77. tristate "Faraday FUSB300 USB Peripheral Controller"
  78. depends on !PHYS_ADDR_T_64BIT && HAS_DMA
  79. help
  80. Faraday usb device controller FUSB300 driver
  81. config USB_FOTG210_UDC
  82. depends on HAS_DMA
  83. tristate "Faraday FOTG210 USB Peripheral Controller"
  84. help
  85. Faraday USB2.0 OTG controller which can be configured as
  86. high speed or full speed USB device. This driver supppors
  87. Bulk Transfer so far.
  88. Say "y" to link the driver statically, or "m" to build a
  89. dynamically linked module called "fotg210_udc".
  90. config USB_GR_UDC
  91. tristate "Aeroflex Gaisler GRUSBDC USB Peripheral Controller Driver"
  92. depends on HAS_DMA
  93. help
  94. Select this to support Aeroflex Gaisler GRUSBDC cores from the GRLIB
  95. VHDL IP core library.
  96. config USB_OMAP
  97. tristate "OMAP USB Device Controller"
  98. depends on ARCH_OMAP1
  99. depends on ISP1301_OMAP || !(MACH_OMAP_H2 || MACH_OMAP_H3)
  100. help
  101. Many Texas Instruments OMAP processors have flexible full
  102. speed USB device controllers, with support for up to 30
  103. endpoints (plus endpoint zero). This driver supports the
  104. controller in the OMAP 1611, and should work with controllers
  105. in other OMAP processors too, given minor tweaks.
  106. Say "y" to link the driver statically, or "m" to build a
  107. dynamically linked module called "omap_udc" and force all
  108. gadget drivers to also be dynamically linked.
  109. config USB_PXA25X
  110. tristate "PXA 25x or IXP 4xx"
  111. depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
  112. help
  113. Intel's PXA 25x series XScale ARM-5TE processors include
  114. an integrated full speed USB 1.1 device controller. The
  115. controller in the IXP 4xx series is register-compatible.
  116. It has fifteen fixed-function endpoints, as well as endpoint
  117. zero (for control transfers).
  118. Say "y" to link the driver statically, or "m" to build a
  119. dynamically linked module called "pxa25x_udc" and force all
  120. gadget drivers to also be dynamically linked.
  121. # if there's only one gadget driver, using only two bulk endpoints,
  122. # don't waste memory for the other endpoints
  123. config USB_PXA25X_SMALL
  124. depends on USB_PXA25X
  125. bool
  126. default n if USB_ETH_RNDIS
  127. default y if USB_ZERO
  128. default y if USB_ETH
  129. default y if USB_G_SERIAL
  130. config USB_R8A66597
  131. tristate "Renesas R8A66597 USB Peripheral Controller"
  132. depends on HAS_DMA
  133. help
  134. R8A66597 is a discrete USB host and peripheral controller chip that
  135. supports both full and high speed USB 2.0 data transfers.
  136. It has nine configurable endpoints, and endpoint zero.
  137. Say "y" to link the driver statically, or "m" to build a
  138. dynamically linked module called "r8a66597_udc" and force all
  139. gadget drivers to also be dynamically linked.
  140. config USB_RENESAS_USBHS_UDC
  141. tristate 'Renesas USBHS controller'
  142. depends on USB_RENESAS_USBHS && HAS_DMA
  143. help
  144. Renesas USBHS is a discrete USB host and peripheral controller chip
  145. that supports both full and high speed USB 2.0 data transfers.
  146. It has nine or more configurable endpoints, and endpoint zero.
  147. Say "y" to link the driver statically, or "m" to build a
  148. dynamically linked module called "renesas_usbhs" and force all
  149. gadget drivers to also be dynamically linked.
  150. config USB_PXA27X
  151. tristate "PXA 27x"
  152. help
  153. Intel's PXA 27x series XScale ARM v5TE processors include
  154. an integrated full speed USB 1.1 device controller.
  155. It has up to 23 endpoints, as well as endpoint zero (for
  156. control transfers).
  157. Say "y" to link the driver statically, or "m" to build a
  158. dynamically linked module called "pxa27x_udc" and force all
  159. gadget drivers to also be dynamically linked.
  160. config USB_S3C2410
  161. tristate "S3C2410 USB Device Controller"
  162. depends on ARCH_S3C24XX
  163. help
  164. Samsung's S3C2410 is an ARM-4 processor with an integrated
  165. full speed USB 1.1 device controller. It has 4 configurable
  166. endpoints, as well as endpoint zero (for control transfers).
  167. This driver has been tested on the S3C2410, S3C2412, and
  168. S3C2440 processors.
  169. config USB_S3C2410_DEBUG
  170. bool "S3C2410 udc debug messages"
  171. depends on USB_S3C2410
  172. config USB_S3C_HSUDC
  173. tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
  174. depends on ARCH_S3C24XX
  175. help
  176. Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
  177. integrated with dual speed USB 2.0 device controller. It has
  178. 8 endpoints, as well as endpoint zero.
  179. This driver has been tested on S3C2416 and S3C2450 processors.
  180. config USB_MV_UDC
  181. tristate "Marvell USB2.0 Device Controller"
  182. depends on HAS_DMA
  183. help
  184. Marvell Socs (including PXA and MMP series) include a high speed
  185. USB2.0 OTG controller, which can be configured as high speed or
  186. full speed USB peripheral.
  187. config USB_MV_U3D
  188. depends on HAS_DMA
  189. tristate "MARVELL PXA2128 USB 3.0 controller"
  190. help
  191. MARVELL PXA2128 Processor series include a super speed USB3.0 device
  192. controller, which support super speed USB peripheral.
  193. #
  194. # Controllers available in both integrated and discrete versions
  195. #
  196. config USB_M66592
  197. tristate "Renesas M66592 USB Peripheral Controller"
  198. help
  199. M66592 is a discrete USB peripheral controller chip that
  200. supports both full and high speed USB 2.0 data transfers.
  201. It has seven configurable endpoints, and endpoint zero.
  202. Say "y" to link the driver statically, or "m" to build a
  203. dynamically linked module called "m66592_udc" and force all
  204. gadget drivers to also be dynamically linked.
  205. source "drivers/usb/gadget/udc/bdc/Kconfig"
  206. #
  207. # Controllers available only in discrete form (and all PCI controllers)
  208. #
  209. config USB_AMD5536UDC
  210. tristate "AMD5536 UDC"
  211. depends on PCI
  212. help
  213. The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
  214. It is a USB Highspeed DMA capable USB device controller. Beside ep0
  215. it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
  216. The UDC port supports OTG operation, and may be used as a host port
  217. if it's not being used to implement peripheral or OTG roles.
  218. Say "y" to link the driver statically, or "m" to build a
  219. dynamically linked module called "amd5536udc" and force all
  220. gadget drivers to also be dynamically linked.
  221. config USB_FSL_QE
  222. tristate "Freescale QE/CPM USB Device Controller"
  223. depends on FSL_SOC && (QUICC_ENGINE || CPM)
  224. help
  225. Some of Freescale PowerPC processors have a Full Speed
  226. QE/CPM2 USB controller, which support device mode with 4
  227. programmable endpoints. This driver supports the
  228. controller in the MPC8360 and MPC8272, and should work with
  229. controllers having QE or CPM2, given minor tweaks.
  230. Set CONFIG_USB_GADGET to "m" to build this driver as a
  231. dynamically linked module called "fsl_qe_udc".
  232. config USB_NET2272
  233. tristate "PLX NET2272"
  234. help
  235. PLX NET2272 is a USB peripheral controller which supports
  236. both full and high speed USB 2.0 data transfers.
  237. It has three configurable endpoints, as well as endpoint zero
  238. (for control transfer).
  239. Say "y" to link the driver statically, or "m" to build a
  240. dynamically linked module called "net2272" and force all
  241. gadget drivers to also be dynamically linked.
  242. config USB_NET2272_DMA
  243. bool "Support external DMA controller"
  244. depends on USB_NET2272 && HAS_DMA
  245. help
  246. The NET2272 part can optionally support an external DMA
  247. controller, but your board has to have support in the
  248. driver itself.
  249. If unsure, say "N" here. The driver works fine in PIO mode.
  250. config USB_NET2280
  251. tristate "NetChip 228x / PLX USB338x"
  252. depends on PCI
  253. help
  254. NetChip 2280 / 2282 is a PCI based USB peripheral controller which
  255. supports both full and high speed USB 2.0 data transfers.
  256. It has six configurable endpoints, as well as endpoint zero
  257. (for control transfers) and several endpoints with dedicated
  258. functions.
  259. PLX 3380 / 3382 is a PCIe based USB peripheral controller which
  260. supports full, high speed USB 2.0 and super speed USB 3.0
  261. data transfers.
  262. It has eight configurable endpoints, as well as endpoint zero
  263. (for control transfers) and several endpoints with dedicated
  264. functions.
  265. Say "y" to link the driver statically, or "m" to build a
  266. dynamically linked module called "net2280" and force all
  267. gadget drivers to also be dynamically linked.
  268. config USB_GOKU
  269. tristate "Toshiba TC86C001 'Goku-S'"
  270. depends on PCI
  271. help
  272. The Toshiba TC86C001 is a PCI device which includes controllers
  273. for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
  274. The device controller has three configurable (bulk or interrupt)
  275. endpoints, plus endpoint zero (for control transfers).
  276. Say "y" to link the driver statically, or "m" to build a
  277. dynamically linked module called "goku_udc" and to force all
  278. gadget drivers to also be dynamically linked.
  279. config USB_EG20T
  280. tristate "Intel QUARK X1000/EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
  281. depends on PCI
  282. help
  283. This is a USB device driver for EG20T PCH.
  284. EG20T PCH is the platform controller hub that is used in Intel's
  285. general embedded platform. EG20T PCH has USB device interface.
  286. Using this interface, it is able to access system devices connected
  287. to USB device.
  288. This driver enables USB device function.
  289. USB device is a USB peripheral controller which
  290. supports both full and high speed USB 2.0 data transfers.
  291. This driver supports both control transfer and bulk transfer modes.
  292. This driver dose not support interrupt transfer or isochronous
  293. transfer modes.
  294. This driver also can be used for LAPIS Semiconductor's ML7213 which is
  295. for IVI(In-Vehicle Infotainment) use.
  296. ML7831 is for general purpose use.
  297. ML7213/ML7831 is companion chip for Intel Atom E6xx series.
  298. ML7213/ML7831 is completely compatible for Intel EG20T PCH.
  299. This driver can be used with Intel's Quark X1000 SOC platform
  300. config USB_GADGET_XILINX
  301. tristate "Xilinx USB Driver"
  302. depends on HAS_DMA
  303. depends on OF || COMPILE_TEST
  304. help
  305. USB peripheral controller driver for Xilinx USB2 device.
  306. Xilinx USB2 device is a soft IP which supports both full
  307. and high speed USB 2.0 data transfers. It has seven configurable
  308. endpoints(bulk or interrupt or isochronous), as well as
  309. endpoint zero(for control transfers).
  310. Say "y" to link the driver statically, or "m" to build a
  311. dynamically linked module called "udc-xilinx" and force all
  312. gadget drivers to also be dynamically linked.
  313. #
  314. # LAST -- dummy/emulated controller
  315. #
  316. config USB_DUMMY_HCD
  317. tristate "Dummy HCD (DEVELOPMENT)"
  318. depends on USB=y || (USB=m && USB_GADGET=m)
  319. help
  320. This host controller driver emulates USB, looping all data transfer
  321. requests back to a USB "gadget driver" in the same host. The host
  322. side is the master; the gadget side is the slave. Gadget drivers
  323. can be high, full, or low speed; and they have access to endpoints
  324. like those from NET2280, PXA2xx, or SA1100 hardware.
  325. This may help in some stages of creating a driver to embed in a
  326. Linux device, since it lets you debug several parts of the gadget
  327. driver without its hardware or drivers being involved.
  328. Since such a gadget side driver needs to interoperate with a host
  329. side Linux-USB device driver, this may help to debug both sides
  330. of a USB protocol stack.
  331. Say "y" to link the driver statically, or "m" to build a
  332. dynamically linked module called "dummy_hcd" and force all
  333. gadget drivers to also be dynamically linked.
  334. # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
  335. # first and will be selected by default.
  336. endmenu