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