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