Kconfig 16 KB

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