2 # USB Gadget support on a system involves
3 # (a) a peripheral controller, and
4 # (b) the gadget driver using it.
6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
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.
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).
17 # USB Peripheral Controller Support
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.
26 menu "USB Peripheral Controller"
29 # Integrated controllers
33 tristate "Atmel AT91 USB Device Port"
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).
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.
45 tristate "LPC32XX USB Peripheral Controller"
46 depends on ARCH_LPC32XX && I2C
49 This option selects the USB device controller in the LPC32xx SoC.
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.
57 depends on AVR32 || ARCH_AT91
59 USBA is the integrated high-speed USB Device controller on
60 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
62 config USB_BCM63XX_UDC
63 tristate "Broadcom BCM63xx Peripheral Controller"
66 Many Broadcom BCM63xx chipsets (such as the BCM6328) have a
67 high speed USB Device Port with support for four fixed endpoints
70 Say "y" to link the driver statically, or "m" to build a
71 dynamically linked module called "bcm63xx_udc".
74 tristate "Freescale Highspeed USB DR Peripheral Controller"
75 depends on FSL_SOC || ARCH_MXC
76 select USB_FSL_MPH_DR_OF if OF
78 Some of Freescale PowerPC and i.MX processors have a High Speed
79 Dual-Role(DR) USB controller, which supports device mode.
81 The number of programmable endpoints is different through
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.
89 tristate "Faraday FUSB300 USB Peripheral Controller"
90 depends on !PHYS_ADDR_T_64BIT && HAS_DMA
92 Faraday usb device controller FUSB300 driver
94 config USB_FOTG210_UDC
96 tristate "Faraday FOTG210 USB Peripheral Controller"
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.
102 Say "y" to link the driver statically, or "m" to build a
103 dynamically linked module called "fotg210_udc".
106 tristate "Aeroflex Gaisler GRUSBDC USB Peripheral Controller Driver"
109 Select this to support Aeroflex Gaisler GRUSBDC cores from the GRLIB
110 VHDL IP core library.
113 tristate "OMAP USB Device Controller"
114 depends on ARCH_OMAP1
115 depends on ISP1301_OMAP || !(MACH_OMAP_H2 || MACH_OMAP_H3)
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.
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.
128 tristate "PXA 25x or IXP 4xx"
129 depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
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.
135 It has fifteen fixed-function endpoints, as well as endpoint
136 zero (for control transfers).
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.
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
147 default n if USB_ETH_RNDIS
148 default y if USB_ZERO
150 default y if USB_G_SERIAL
153 tristate "Renesas R8A66597 USB Peripheral Controller"
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.
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.
164 config USB_RENESAS_USBHS_UDC
165 tristate 'Renesas USBHS controller'
166 depends on USB_RENESAS_USBHS && HAS_DMA
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.
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.
179 Intel's PXA 27x series XScale ARM v5TE processors include
180 an integrated full speed USB 1.1 device controller.
182 It has up to 23 endpoints, as well as endpoint zero (for
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.
190 tristate "S3C2410 USB Device Controller"
191 depends on ARCH_S3C24XX
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).
197 This driver has been tested on the S3C2410, S3C2412, and
200 config USB_S3C2410_DEBUG
201 bool "S3C2410 udc debug messages"
202 depends on USB_S3C2410
205 tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
206 depends on ARCH_S3C24XX
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.
212 This driver has been tested on S3C2416 and S3C2450 processors.
215 tristate "Marvell USB2.0 Device Controller"
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.
224 tristate "MARVELL PXA2128 USB 3.0 controller"
226 MARVELL PXA2128 Processor series include a super speed USB3.0 device
227 controller, which support super speed USB peripheral.
230 # Controllers available in both integrated and discrete versions
234 tristate "Renesas M66592 USB Peripheral Controller"
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.
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.
244 source "drivers/usb/gadget/udc/bdc/Kconfig"
247 # Controllers available only in discrete form (and all PCI controllers)
250 config USB_AMD5536UDC
251 tristate "AMD5536 UDC"
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.
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.
265 tristate "Freescale QE/CPM USB Device Controller"
266 depends on FSL_SOC && (QUICC_ENGINE || CPM)
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.
274 Set CONFIG_USB_GADGET to "m" to build this driver as a
275 dynamically linked module called "fsl_qe_udc".
278 tristate "PLX NET2272"
280 PLX NET2272 is a USB peripheral controller which supports
281 both full and high speed USB 2.0 data transfers.
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.
289 config USB_NET2272_DMA
290 bool "Support external DMA controller"
291 depends on USB_NET2272 && HAS_DMA
293 The NET2272 part can optionally support an external DMA
294 controller, but your board has to have support in the
297 If unsure, say "N" here. The driver works fine in PIO mode.
300 tristate "NetChip 228x / PLX USB338x"
303 NetChip 2280 / 2282 is a PCI based USB peripheral controller which
304 supports both full and high speed USB 2.0 data transfers.
306 It has six configurable endpoints, as well as endpoint zero
307 (for control transfers) and several endpoints with dedicated
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
314 It has eight configurable endpoints, as well as endpoint zero
315 (for control transfers) and several endpoints with dedicated
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.
323 tristate "Toshiba TC86C001 'Goku-S'"
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).
329 The device controller has three configurable (bulk or interrupt)
330 endpoints, plus endpoint zero (for control transfers).
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.
337 tristate "Intel QUARK X1000/EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
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
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
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.
358 This driver can be used with Intel's Quark X1000 SOC platform
360 config USB_GADGET_XILINX
361 tristate "Xilinx USB Driver"
363 depends on OF || COMPILE_TEST
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).
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.
376 # LAST -- dummy/emulated controller
380 tristate "Dummy HCD (DEVELOPMENT)"
381 depends on USB=y || (USB=m && USB_GADGET=m)
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.
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.
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.
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.
401 # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
402 # first and will be selected by default.