2005-04-17 02:20:36 +04:00
#
# USB device configuration
#
2013-08-10 05:17:48 +04:00
config USB_OHCI_BIG_ENDIAN_DESC
bool
config USB_OHCI_BIG_ENDIAN_MMIO
bool
config USB_OHCI_LITTLE_ENDIAN
bool
default n if STB03xxx || PPC_MPC52xx
default y
config USB_EHCI_BIG_ENDIAN_MMIO
bool
config USB_EHCI_BIG_ENDIAN_DESC
bool
2012-03-23 01:01:07 +04:00
menuconfig USB_SUPPORT
bool "USB support"
depends on HAS_IOMEM
default y
---help---
This option adds core support for Universal Serial Bus (USB).
You will also need drivers from the following menu to make use of it.
2012-03-14 02:58:05 +04:00
if USB_SUPPORT
config USB_COMMON
tristate
config USB_ARCH_HAS_HCD
2013-06-04 21:42:22 +04:00
def_bool y
2012-03-14 02:58:05 +04:00
2005-04-17 02:20:36 +04:00
config USB
tristate "Support for Host-side USB"
depends on USB_ARCH_HAS_HCD
2016-03-23 19:45:08 +03:00
select USB_COMMON
2009-04-24 12:12:18 +04:00
select NLS # for UTF-8 strings
2005-04-17 02:20:36 +04:00
---help---
Universal Serial Bus (USB) is a specification for a serial bus
subsystem which offers higher speeds and more features than the
traditional PC serial port. The bus supplies power to peripherals
and allows for hot swapping. Up to 127 USB peripherals can be
connected to a single USB host in a tree structure.
The USB host is the root of the tree, the peripherals are the
leaves and the inner nodes are special USB devices called hubs.
Most PCs now have USB host ports, used to connect peripherals
such as scanners, keyboards, mice, modems, cameras, disks,
flash memory, network links, and printers to the PC.
Say Y here if your computer has a host-side USB port and you want
to use USB devices. You then need to say Y to at least one of the
Host Controller Driver (HCD) options below. Choose a USB 1.1
controller, such as "UHCI HCD support" or "OHCI HCD support",
and "EHCI HCD (USB 2.0) support" except for older systems that
do not have USB 2.0 support. It doesn't normally hurt to select
them all if you are not certain.
If your system has a device-side USB port, used in the peripheral
side of the USB protocol, see the "USB Gadget" framework instead.
After choosing your HCD, then select drivers for the USB peripherals
you'll be using. You may want to check out the information provided
in <file:Documentation/usb/> and especially the links given in
<file:Documentation/usb/usb-help.txt>.
To compile this driver as a module, choose M here: the
module will be called usbcore.
2017-02-25 14:20:55 +03:00
config USB_PCI
bool "PCI based USB host interface"
depends on PCI
default y
---help---
A lot of embeded system SOC (e.g. freescale T2080) have both
PCI and USB modules. But USB module is controlled by registers
directly, it have no relationship with PCI module.
When say N here it will not build PCI related code in USB driver.
2013-04-09 16:29:25 +04:00
if USB
2005-04-17 02:20:36 +04:00
2013-04-09 16:29:25 +04:00
source "drivers/usb/core/Kconfig"
usb: Introduce DesignWare USB3 DRD Driver
The DesignWare USB3 is a highly
configurable IP Core which can be
instantiated as Dual-Role Device (DRD),
Peripheral Only and Host Only (XHCI)
configurations.
Several other parameters can be configured
like amount of FIFO space, amount of TX and
RX endpoints, amount of Host Interrupters,
etc.
The current driver has been validated with
a virtual model of version 1.73a of that core
and with an FPGA burned with version 1.83a
of the DRD core. We have support for PCIe
bus, which is used on FPGA prototyping, and
for the OMAP5, more adaptation (or glue)
layers can be easily added and the driver
is half prepared to handle any possible
configuration the HW engineer has chosen
considering we have the information on
one of the GHWPARAMS registers to do
runtime checking of certain features.
More runtime checks can, and should, be added
in order to make this driver even more flexible
with regards to number of endpoints, FIFO sizes,
transfer types, etc.
While this supports only the device side, for
now, we will add support for Host side (xHCI -
see the updated series Sebastian has sent [1])
and OTG after we have it all stabilized.
[1] http://marc.info/?l=linux-usb&m=131341992020339&w=2
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2011-08-19 19:10:58 +04:00
2008-07-21 23:44:50 +04:00
source "drivers/usb/mon/Kconfig"
2008-09-17 19:34:26 +04:00
source "drivers/usb/wusbcore/Kconfig"
2005-04-17 02:20:36 +04:00
source "drivers/usb/host/Kconfig"
2011-04-04 08:44:59 +04:00
source "drivers/usb/renesas_usbhs/Kconfig"
2005-04-17 02:20:36 +04:00
source "drivers/usb/class/Kconfig"
source "drivers/usb/storage/Kconfig"
source "drivers/usb/image/Kconfig"
2014-08-20 08:31:00 +04:00
source "drivers/usb/usbip/Kconfig"
2013-04-09 16:29:25 +04:00
endif
2016-10-19 05:28:23 +03:00
source "drivers/usb/mtu3/Kconfig"
2013-12-22 07:08:33 +04:00
source "drivers/usb/musb/Kconfig"
2013-04-09 16:29:25 +04:00
source "drivers/usb/dwc3/Kconfig"
2014-01-14 01:50:09 +04:00
source "drivers/usb/dwc2/Kconfig"
2013-04-09 16:29:25 +04:00
source "drivers/usb/chipidea/Kconfig"
2015-01-21 01:56:02 +03:00
source "drivers/usb/isp1760/Kconfig"
2005-04-17 02:20:36 +04:00
comment "USB port drivers"
2013-04-09 16:29:25 +04:00
if USB
2005-04-17 02:20:36 +04:00
config USB_USS720
tristate "USS720 parport driver"
2013-04-09 16:29:25 +04:00
depends on PARPORT
2005-04-17 02:20:36 +04:00
select PARPORT_NOT_PC
---help---
This driver is for USB parallel port adapters that use the Lucent
Technologies USS-720 chip. These cables are plugged into your USB
port and provide USB compatibility to peripherals designed with
parallel port interfaces.
The chip has two modes: automatic mode and manual mode. In automatic
mode, it looks to the computer like a standard USB printer. Only
printers may be connected to the USS-720 in this mode. The generic
USB printer driver ("USB Printer support", above) may be used in
that mode, and you can say N here if you want to use the chip only
in this mode.
Manual mode is not limited to printers, any parallel port
device should work. This driver utilizes manual mode.
Note however that some operations are three orders of magnitude
slower than on a PCI/ISA Parallel Port, so timing critical
applications might not work.
Say Y here if you own an USS-720 USB->Parport cable and intend to
connect anything other than a printer to it.
To compile this driver as a module, choose M here: the
module will be called uss720.
source "drivers/usb/serial/Kconfig"
source "drivers/usb/misc/Kconfig"
source "drivers/usb/atm/Kconfig"
2013-04-09 16:29:25 +04:00
endif # USB
source "drivers/usb/phy/Kconfig"
2005-04-17 02:20:36 +04:00
source "drivers/usb/gadget/Kconfig"
2017-03-21 14:56:47 +03:00
source "drivers/usb/typec/Kconfig"
2014-09-25 00:43:21 +04:00
config USB_LED_TRIG
bool "USB LED Triggers"
2016-09-14 04:49:30 +03:00
depends on LEDS_CLASS && LEDS_TRIGGERS
select USB_COMMON
2014-09-25 00:43:21 +04:00
help
This option adds LED triggers for USB host and/or gadget activity.
Say Y here if you are working on a system with led-class supported
LEDs and you want to use them as activity indicators for USB host or
gadget.
2016-08-16 12:33:25 +03:00
config USB_ULPI_BUS
tristate "USB ULPI PHY interface support"
2016-09-14 04:49:30 +03:00
select USB_COMMON
2016-08-16 12:33:25 +03:00
help
UTMI+ Low Pin Interface (ULPI) is specification for a commonly used
USB 2.0 PHY interface. The ULPI specification defines a standard set
of registers that can be used to detect the vendor and product which
allows ULPI to be handled as a bus. This module is the driver for that
bus.
The ULPI interfaces (the buses) are registered by the drivers for USB
controllers which support ULPI register access and have ULPI PHY
attached to them. The ULPI PHY drivers themselves are normal PHY
drivers.
ULPI PHYs provide often functions such as ADP sensing/probing (OTG
protocol) and USB charger detection.
To compile this driver as a module, choose M here: the module will
be called ulpi.
2007-05-11 10:04:13 +04:00
endif # USB_SUPPORT