Kconfig 18 KB

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