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