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