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