# SPDX-License-Identifier: GPL-2.0
#
# [31mCONFIG_USB[0m Gadget support on a system involves
# (a) a peripheral controller, and
# (b) the gadget driver using it.
#
# NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
#
# - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
# - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
# - Some systems have both kinds of controllers.
#
# With help from a special transceiver and a "Mini-AB" jack, systems with
# both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
#
#
# [31mCONFIG_USB[0m Peripheral Controller Support
#
# The order here is alphabetical, except that integrated controllers go
# before discrete ones so they will be the initial/default value:
# - integrated/SOC controllers first
# - licensed IP used in both SOC and discrete versions
# - discrete ones (including all [31mCONFIG_PCI[0m-only controllers)
# - debug/dummy gadget+hcd is last.
#
menu "USB Peripheral Controller"
#
# Integrated controllers
#
config [31mCONFIG_USB_AT91[0m
tristate "Atmel AT91 USB Device Port"
depends on [31mCONFIG_ARCH_AT91[0m
depends on [31mCONFIG_OF[0m || [31mCONFIG_COMPILE_TEST[0m
help
Many Atmel AT91 processors (such as the AT91RM2000) have a
full speed [31mCONFIG_USB[0m Device Port with support for five configurable
endpoints (plus endpoint zero).
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "at91_udc" and force all
gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_LPC32XX[0m
tristate "LPC32XX USB Peripheral Controller"
depends on [31mCONFIG_ARCH_LPC32XX[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_I2C[0m
select [31mCONFIG_USB_ISP1301[0m
help
This option selects the [31mCONFIG_USB[0m device controller in the LPC32xx SoC.
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "lpc32xx_udc" and force all
gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_ATMEL_USBA[0m
tristate "Atmel USBA"
depends on [31mCONFIG_ARCH_AT91[0m
help
USBA is the integrated high-speed [31mCONFIG_USB[0m Device controller on
the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
The fifo_mode parameter is used to select endpoint allocation mode.
fifo_mode = 0 is used to let the driver autoconfigure the endpoints.
In this case, for ep1 2 banks are allocated if it works in isochronous
mode and only 1 bank otherwise. For the rest of the endpoints
only 1 bank is allocated.
fifo_mode = 1 is a generic maximum fifo size (1024 bytes) configuration
allowing the usage of ep1 - ep6
fifo_mode = 2 is a generic performance maximum fifo size (1024 bytes)
configuration allowing the usage of ep1 - ep3
fifo_mode = 3 is a balanced performance configuration allowing the
the usage of ep1 - ep8
config [31mCONFIG_USB_BCM63XX_UDC[0m
tristate "Broadcom BCM63xx Peripheral Controller"
depends on [31mCONFIG_BCM63XX[0m
help
Many Broadcom BCM63xx chipsets (such as the BCM6328) have a
high speed [31mCONFIG_USB[0m Device Port with support for four fixed endpoints
(plus endpoint zero).
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "bcm63xx_udc".
config [31mCONFIG_USB_FSL_USB2[0m
tristate "Freescale Highspeed USB DR Peripheral Controller"
depends on [31mCONFIG_FSL_SOC[0m || [31mCONFIG_ARCH_MXC[0m
help
Some of Freescale PowerPC and i.MX processors have a High Speed
Dual-Role(DR) [31mCONFIG_USB[0m controller, which supports device mode.
The number of programmable endpoints is different through
SOC revisions.
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "fsl_usb2_udc" and force
all gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_FUSB300[0m
tristate "Faraday FUSB300 USB Peripheral Controller"
depends on ![31mCONFIG_PHYS_ADDR_T_64BIT[0m && [31mCONFIG_HAS_DMA[0m
help
Faraday usb device controller FUSB300 driver
config [31mCONFIG_USB_FOTG210_UDC[0m
depends on [31mCONFIG_HAS_DMA[0m
tristate "Faraday FOTG210 USB Peripheral Controller"
help
Faraday USB2.0 OTG controller which can be configured as
high speed or full speed [31mCONFIG_USB[0m device. This driver supppors
Bulk Transfer so far.
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "fotg210_udc".
config [31mCONFIG_USB_GR_UDC[0m
tristate "Aeroflex Gaisler GRUSBDC USB Peripheral Controller Driver"
depends on [31mCONFIG_HAS_DMA[0m
help
Select this to support Aeroflex Gaisler GRUSBDC cores from the GRLIB
VHDL IP core library.
config [31mCONFIG_USB_OMAP[0m
tristate "OMAP USB Device Controller"
depends on [31mCONFIG_ARCH_OMAP1[0m
depends on [31mCONFIG_ISP1301_OMAP[0m || !([31mCONFIG_MACH_OMAP_H2[0m || [31mCONFIG_MACH_OMAP_H3[0m)
help
Many Texas Instruments OMAP processors have flexible full
speed [31mCONFIG_USB[0m device controllers, with support for up to 30
endpoints (plus endpoint zero). This driver supports the
controller in the OMAP 1611, and should work with controllers
in other OMAP processors too, given minor tweaks.
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "omap_udc" and force all
gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_PXA25X[0m
tristate "PXA 25x or IXP 4xx"
depends on ([31mCONFIG_ARCH_PXA[0m && [31mCONFIG_PXA25x[0m) || [31mCONFIG_ARCH_IXP4XX[0m
depends on [31mCONFIG_HAS_IOMEM[0m
help
Intel's PXA 25x series XScale [31mCONFIG_ARM[0m-5TE processors include
an integrated full speed [31mCONFIG_USB[0m 1.1 device controller. The
controller in the IXP [31mCONFIG_4xx[0m series is register-compatible.
It has fifteen fixed-function endpoints, as well as endpoint
zero (for control transfers).
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "pxa25x_udc" and force all
gadget drivers to also be dynamically linked.
# if there's only one gadget driver, using only two bulk endpoints,
# don't waste memory for the other endpoints
config [31mCONFIG_USB_PXA25X_SMALL[0m
depends on [31mCONFIG_USB_PXA25X[0m
bool
default n if [31mCONFIG_USB_ETH_RNDIS[0m
default y if [31mCONFIG_USB_ZERO[0m
default y if [31mCONFIG_USB_ETH[0m
default y if [31mCONFIG_USB_G_SERIAL[0m
config [31mCONFIG_USB_R8A66597[0m
tristate "Renesas R8A66597 USB Peripheral Controller"
depends on [31mCONFIG_HAS_DMA[0m
help
R8A66597 is a discrete [31mCONFIG_USB[0m host and peripheral controller chip that
supports both full and high speed [31mCONFIG_USB[0m 2.0 data transfers.
It has nine configurable endpoints, and endpoint zero.
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "r8a66597_udc" and force all
gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_RENESAS_USBHS_UDC[0m
tristate 'Renesas USBHS controller'
depends on [31mCONFIG_USB_RENESAS_USBHS[0m
help
Renesas USBHS is a discrete [31mCONFIG_USB[0m host and peripheral controller chip
that supports both full and high speed [31mCONFIG_USB[0m 2.0 data transfers.
It has nine or more configurable endpoints, and endpoint zero.
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "renesas_usbhs" and force all
gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_RENESAS_USB3[0m
tristate 'Renesas USB3.0 Peripheral controller'
depends on [31mCONFIG_ARCH_RENESAS[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_EXTCON[0m
select [31mCONFIG_USB_ROLE_SWITCH[0m
help
Renesas USB3.0 Peripheral controller is a [31mCONFIG_USB[0m peripheral controller
that supports super, high, and full speed [31mCONFIG_USB[0m 3.0 data transfers.
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "renesas_usb3" and force all
gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_PXA27X[0m
tristate "PXA 27x"
depends on [31mCONFIG_HAS_IOMEM[0m
help
Intel's PXA 27x series XScale [31mCONFIG_ARM[0m v5TE processors include
an integrated full speed [31mCONFIG_USB[0m 1.1 device controller.
It has up to 23 endpoints, as well as endpoint zero (for
control transfers).
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "pxa27x_udc" and force all
gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_S3C2410[0m
tristate "S3C2410 USB Device Controller"
depends on [31mCONFIG_ARCH_S3C24XX[0m
help
Samsung's S3C2410 is an [31mCONFIG_ARM[0m-4 processor with an integrated
full speed [31mCONFIG_USB[0m 1.1 device controller. It has 4 configurable
endpoints, as well as endpoint zero (for control transfers).
This driver has been tested on the S3C2410, S3C2412, and
S3C2440 processors.
config [31mCONFIG_USB_S3C2410_DEBUG[0m
bool "S3C2410 udc debug messages"
depends on [31mCONFIG_USB_S3C2410[0m
config [31mCONFIG_USB_S3C_HSUDC[0m
tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
depends on [31mCONFIG_ARCH_S3C24XX[0m
help
Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
integrated with dual speed [31mCONFIG_USB[0m 2.0 device controller. It has
8 endpoints, as well as endpoint zero.
This driver has been tested on S3C2416 and S3C2450 processors.
config [31mCONFIG_USB_MV_UDC[0m
tristate "Marvell USB2.0 Device Controller"
depends on [31mCONFIG_HAS_DMA[0m
help
Marvell Socs (including PXA and MMP series) include a high speed
USB2.0 OTG controller, which can be configured as high speed or
full speed [31mCONFIG_USB[0m peripheral.
config [31mCONFIG_USB_MV_U3D[0m
depends on [31mCONFIG_HAS_DMA[0m
tristate "MARVELL PXA2128 USB 3.0 controller"
help
MARVELL PXA2128 Processor series include a super speed USB3.0 device
controller, which support super speed [31mCONFIG_USB[0m peripheral.
config [31mCONFIG_USB_SNP_CORE[0m
depends on ([31mCONFIG_USB_AMD5536UDC[0m || [31mCONFIG_USB_SNP_UDC_PLAT[0m)
depends on [31mCONFIG_HAS_DMA[0m
tristate
help
This enables core driver support for Synopsys [31mCONFIG_USB[0m 2.0 Device
controller.
This will be enabled when [31mCONFIG_PCI[0m or Platform driver for this UDC is
selected. Currently, this will be enabled by [31mCONFIG_USB_SNP_UDC_PLAT[0m or
[31mCONFIG_USB_AMD5536UDC[0m options.
This IP is different to the High Speed OTG IP that can be enabled
by selecting [31mCONFIG_USB_DWC2[0m or [31mCONFIG_USB_DWC3[0m options.
config [31mCONFIG_USB_SNP_UDC_PLAT[0m
tristate "Synopsys USB 2.0 Device controller"
depends on [31mCONFIG_USB_GADGET[0m && [31mCONFIG_OF[0m && [31mCONFIG_HAS_DMA[0m
depends on [31mCONFIG_EXTCON[0m || [31mCONFIG_EXTCON[0m=n
select [31mCONFIG_USB_SNP_CORE[0m
default [31mCONFIG_ARCH_BCM_IPROC[0m
help
This adds Platform Device support for Synopsys Designware core
AHB subsystem USB2.0 Device Controller (UDC).
This driver works with UDCs integrated into Broadcom's Northstar2
and Cygnus SoCs.
If unsure, say N.
#
# Controllers available in both integrated and discrete versions
#
config [31mCONFIG_USB_M66592[0m
tristate "Renesas M66592 USB Peripheral Controller"
depends on [31mCONFIG_HAS_IOMEM[0m
help
M66592 is a discrete [31mCONFIG_USB[0m peripheral controller chip that
supports both full and high speed [31mCONFIG_USB[0m 2.0 data transfers.
It has seven configurable endpoints, and endpoint zero.
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "m66592_udc" and force all
gadget drivers to also be dynamically linked.
source "drivers/usb/gadget/udc/bdc/Kconfig"
#
# Controllers available only in discrete form (and all [31mCONFIG_PCI[0m controllers)
#
config [31mCONFIG_USB_AMD5536UDC[0m
tristate "AMD5536 UDC"
depends on [31mCONFIG_USB_PCI[0m
select [31mCONFIG_USB_SNP_CORE[0m
help
The AMD5536 UDC is part of the AMD Geode [31mCONFIG_CS5536[0m, an x86 southbridge.
It is a [31mCONFIG_USB[0m Highspeed DMA capable [31mCONFIG_USB[0m device controller. Beside ep0
it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
The UDC port supports OTG operation, and may be used as a host port
if it's not being used to implement peripheral or OTG roles.
This UDC is based on Synopsys [31mCONFIG_USB[0m device controller IP and selects
CONFIG_USB_SNP_CORE option to build the core driver.
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "amd5536udc" and force all
gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_FSL_QE[0m
tristate "Freescale QE/CPM USB Device Controller"
depends on [31mCONFIG_FSL_SOC[0m && ([31mCONFIG_QUICC_ENGINE[0m || [31mCONFIG_CPM[0m)
help
Some of Freescale PowerPC processors have a Full Speed
QE/[31mCONFIG_CPM2[0m [31mCONFIG_USB[0m controller, which support device mode with 4
programmable endpoints. This driver supports the
controller in the MPC8360 and MPC8272, and should work with
controllers having QE or [31mCONFIG_CPM2[0m, given minor tweaks.
Set CONFIG_USB_GADGET to "m" to build this driver as a
dynamically linked module called "fsl_qe_udc".
config [31mCONFIG_USB_NET2272[0m
depends on [31mCONFIG_HAS_IOMEM[0m
tristate "PLX NET2272"
help
PLX NET2272 is a [31mCONFIG_USB[0m peripheral controller which supports
both full and high speed [31mCONFIG_USB[0m 2.0 data transfers.
It has three configurable endpoints, as well as endpoint zero
(for control transfer).
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "net2272" and force all
gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_NET2272_DMA[0m
bool "Support external DMA controller"
depends on [31mCONFIG_USB_NET2272[0m && [31mCONFIG_HAS_DMA[0m
help
The NET2272 part can optionally support an external DMA
controller, but your board has to have support in the
driver itself.
If unsure, say "N" here. The driver works fine in PIO mode.
config [31mCONFIG_USB_NET2280[0m
tristate "NetChip NET228x / PLX USB3x8x"
depends on [31mCONFIG_USB_PCI[0m
help
NetChip 2280 / 2282 is a [31mCONFIG_PCI[0m based [31mCONFIG_USB[0m peripheral controller which
supports both full and high speed [31mCONFIG_USB[0m 2.0 data transfers.
It has six configurable endpoints, as well as endpoint zero
(for control transfers) and several endpoints with dedicated
functions.
PLX 2380 is a PCIe version of the PLX 2380.
PLX 3380 / 3382 is a PCIe based [31mCONFIG_USB[0m peripheral controller which
supports full, high speed [31mCONFIG_USB[0m 2.0 and super speed [31mCONFIG_USB[0m 3.0
data transfers.
It has eight configurable endpoints, as well as endpoint zero
(for control transfers) and several endpoints with dedicated
functions.
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "net2280" and force all
gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_GOKU[0m
tristate "Toshiba TC86C001 'Goku-S'"
depends on [31mCONFIG_USB_PCI[0m
help
The Toshiba TC86C001 is a [31mCONFIG_PCI[0m device which includes controllers
for full speed [31mCONFIG_USB[0m devices, [31mCONFIG_IDE[0m, [31mCONFIG_I2C[0m, SIO, plus a [31mCONFIG_USB[0m host (OHCI).
The device controller has three configurable (bulk or interrupt)
endpoints, plus endpoint zero (for control transfers).
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "goku_udc" and to force all
gadget drivers to also be dynamically linked.
config [31mCONFIG_USB_EG20T[0m
tristate "Intel QUARK X1000/EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
depends on [31mCONFIG_USB_PCI[0m
help
This is a [31mCONFIG_USB[0m device driver for EG20T PCH.
EG20T PCH is the platform controller hub that is used in Intel's
general embedded platform. EG20T PCH has [31mCONFIG_USB[0m device interface.
Using this interface, it is able to access system devices connected
to [31mCONFIG_USB[0m device.
This driver enables [31mCONFIG_USB[0m device function.
[31mCONFIG_USB[0m device is a [31mCONFIG_USB[0m peripheral controller which
supports both full and high speed [31mCONFIG_USB[0m 2.0 data transfers.
This driver supports both control transfer and bulk transfer modes.
This driver dose not support interrupt transfer or isochronous
transfer modes.
This driver also can be used for LAPIS Semiconductor's ML7213 which is
for IVI(In-Vehicle Infotainment) use.
ML7831 is for general purpose use.
ML7213/ML7831 is companion chip for Intel Atom E6xx series.
ML7213/ML7831 is completely compatible for Intel EG20T PCH.
This driver can be used with Intel's Quark X1000 SOC platform
config [31mCONFIG_USB_GADGET_XILINX[0m
tristate "Xilinx USB Driver"
depends on [31mCONFIG_HAS_DMA[0m
depends on [31mCONFIG_OF[0m || [31mCONFIG_COMPILE_TEST[0m
help
[31mCONFIG_USB[0m peripheral controller driver for Xilinx USB2 device.
Xilinx USB2 device is a soft IP which supports both full
and high speed [31mCONFIG_USB[0m 2.0 data transfers. It has seven configurable
endpoints(bulk or interrupt or isochronous), as well as
endpoint zero(for control transfers).
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "udc-xilinx" and force all
gadget drivers to also be dynamically linked.
source "drivers/usb/gadget/udc/aspeed-vhub/Kconfig"
#
# LAST -- dummy/emulated controller
#
config [31mCONFIG_USB_DUMMY_HCD[0m
tristate "Dummy HCD (DEVELOPMENT)"
depends on [31mCONFIG_USB[0m=y || ([31mCONFIG_USB[0m=m && [31mCONFIG_USB_GADGET[0m=m)
help
This host controller driver emulates [31mCONFIG_USB[0m, looping all data transfer
requests back to a [31mCONFIG_USB[0m "gadget driver" in the same host. The host
side is the master; the gadget side is the slave. Gadget drivers
can be high, full, or low speed; and they have access to endpoints
like those from NET2280, PXA2xx, or SA1100 hardware.
This may help in some stages of creating a driver to embed in a
Linux device, since it lets you debug several parts of the gadget
driver without its hardware or drivers being involved.
Since such a gadget side driver needs to interoperate with a host
side Linux-[31mCONFIG_USB[0m device driver, this may help to debug both sides
of a [31mCONFIG_USB[0m protocol stack.
Say "y" to link the driver statically, or "m" to build a
dynamically linked module called "dummy_hcd" and force all
gadget drivers to also be dynamically linked.
# NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
# first and will be selected by default.
endmenu