Lines Matching +full:usb +full:- +full:controller
1 # SPDX-License-Identifier: GPL-2.0
3 # USB Host Controller Drivers
5 comment "USB Host Controller Drivers"
11 The Cypress C67x00 (EZ-Host/EZ-OTG) chips are dual-role
12 host/peripheral/OTG USB controllers.
14 Enable this option to support this chip in host controller mode.
21 tristate "xHCI HCD (USB 3.0) support"
24 The eXtensible Host Controller Interface (xHCI) is standard for USB 3.0
25 "SuperSpeed" host controller hardware.
28 module will be called xhci-hcd.
47 tristate "Support for additional Renesas xHCI controller with firmware"
49 Say 'Y' to enable the support for the Renesas xHCI controller with
69 Say 'Y' to enable the support for the xHCI host controller
77 Say 'Y' to enable the support for the xHCI host controller
87 Say 'Y' to enable the support for the xHCI host controller
91 tristate "xHCI support for Renesas R-Car SoCs"
95 Say 'Y' to enable the support for the xHCI host controller
96 found in Renesas R-Car ARM SoCs.
104 Say 'Y' to enable the support for the xHCI host controller
113 tristate "Broadcom STB USB support"
123 modules will be called ohci-platform.ko, ehci-brcm.ko and
124 xhci-plat-hcd.ko
130 tristate "EHCI HCD (USB 2.0) support"
133 The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0
134 "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware.
135 If your USB host controller supports USB 2.0, you will likely want to
136 configure this Host Controller Driver.
139 or UHCI) to handle USB 1.1 devices connected to root hub ports. Ports
141 connect to a companion controller. If you configure EHCI, you should
142 probably configure the OHCI (for NEC and some other vendors) USB Host
143 Controller Driver or UHCI (for Via motherboards) Host Controller
146 You may want to read <file:Documentation/usb/ehci.rst>.
149 module will be called ehci-hcd.
155 Some EHCI chips have vendor-specific extensions to integrate
157 controller is needed. It's safe to say "y" even if your
158 controller doesn't support this feature.
170 (TT) in USB 2.0 hubs. Without this, only one transfer will be
175 highspeed USB hub which is connected to a highspeed USB Host
176 Controller, and some of those devices will not work correctly
177 (possibly due to "ENOSPC" or "-28" errors), say Y. Conversely, if
191 bool "Use Xilinx usb host EHCI controller core"
196 Xilinx xps USB host controller core is EHCI compliant and has
197 transaction translator built-in. It can be configured to either
202 tristate "Support for Freescale on-chip EHCI USB controller"
205 Variation of ARC USB block used in some Freescale chips.
208 tristate "Support for Nuvoton NPCM7XX on-chip EHCI USB controller"
212 Enables support for the on-chip EHCI controller on
221 Enables support for the on-chip EHCI controller on
225 tristate "Support for Marvell EBU on-chip EHCI USB controller"
229 Enables support for the on-chip EHCI controller on Marvell's
233 Marvell PXA/MMP USB controller" for those.
236 tristate "Support for ST SPEAr on-chip EHCI USB controller"
240 Enables support for the on-chip EHCI controller on
244 tristate "Support for ST STiHxxx on-chip EHCI USB controller"
249 Enable support for the on-chip EHCI controller found on
253 tristate "Support for Atmel on-chip EHCI USB controller"
257 Enables support for the on-chip EHCI controller on
271 Enable support for the internal USB Host Controllers
275 bool "EHCI support for PPC USB controller on OF platform bus"
279 Enables support for the USB controller present on the PowerPC
283 bool "EHCI support for SuperH USB controller"
286 Enables support for the on-chip EHCI controller on the SuperH.
287 If you use the PCI EHCI controller, this option is not necessary.
293 Enable support for the Samsung Exynos SOC's on-chip EHCI controller.
296 tristate "EHCI support for Marvell PXA/MMP USB controller"
300 Enables support for Marvell (including PXA and MMP series) on-chip
301 USB SPH and OTG controller. SPH is a single port host, and it can
302 only be EHCI host. OTG is controller that can switch to host mode.
304 controller used by the EBU-type SoCs including Orion, Kirkwood,
306 on-chip EHCI USB controller" for those.
316 Enable support for the CNS3XXX SOC's on-chip EHCI controller.
317 It is needed for high-speed (480Mbit/sec) USB 2.0 device
329 bool "Octeon on-chip EHCI support (DEPRECATED)"
337 Enable support for the Octeon II SOC's on-chip EHCI
338 controller. It is needed for high-speed (480Mbit/sec)
339 USB 2.0 device support. All CN6XXX based chips with USB are
348 The OXU210HP is an USB host/OTG/device controller. Enable this
352 implement OTG nor USB device controllers.
355 module will be called oxu210hp-hcd.
361 The ISP1160 and ISP1161 chips are USB host controllers. Enable this
367 module will be called isp116x-hcd.
374 Supports the Philips ISP1362 chip as a host controller
379 module will be called isp1362-hcd.
383 depends on USB && HAS_DMA && HAS_IOMEM
385 Faraday FOTG210 is an OTG controller which can be configured as
390 module will be called fotg210-hcd.
393 tristate "MAX3421 HCD (USB-over-SPI) support"
394 depends on USB && SPI
396 The Maxim MAX3421E chip supports standard USB 2.0-compliant
397 full-speed devices either in host or peripheral mode. This
398 driver supports the host-mode of the MAX3421E only.
401 be called max3421-hcd.
404 tristate "OHCI HCD (USB 1.1) support"
407 The Open Host Controller Interface (OHCI) is a standard for accessing
408 USB 1.1 host controller hardware. It does more in hardware than Intel's
409 UHCI specification. If your USB host controller follows the OHCI spec,
410 say Y. On most non-x86 systems, and on x86 hardware that's not using a
411 USB controller from Intel or VIA, this is appropriate. If your host
412 controller doesn't use PCI, this is probably appropriate. For a PCI
413 based system where you're not sure, the "lspci -v" entry will list the
414 right "prog-if" for your USB controller(s): EHCI, OHCI, or UHCI.
417 module will be called ohci-hcd.
427 Enables support for the OHCI controller on OMAP1/2 chips.
430 tristate "Support for ST SPEAr on-chip OHCI USB controller"
434 Enables support for the on-chip OHCI controller on
438 tristate "Support for ST STiHxxx on-chip OHCI USB controller"
443 Enable support for the on-chip OHCI controller found on
451 Enables support for the on-chip OHCI controller on
455 tristate "Support for LPC on-chip OHCI USB controller"
461 Enables support for the on-chip OHCI controller on
465 tristate "Support for PXA27X/PXA3XX on-chip OHCI USB controller"
469 Enables support for the on-chip OHCI controller on
473 tristate "Support for Atmel on-chip OHCI USB controller"
477 Enables support for the on-chip OHCI controller on
489 Enables support for the on-chip OHCI controller on
500 controller. This driver cannot currently be a loadable
509 Enables support for big-endian USB controllers present on the
517 Enables support for little-endian USB controllers present on the
526 tristate "OHCI support for PCI-bus USB controllers"
531 Enables support for PCI-bus plug-in USB controller cards.
544 Broadcom USB OHCI core.
552 bool "OHCI support for SuperH USB controller (DEPRECATED)"
559 Enables support for the on-chip OHCI controller on the SuperH.
560 If you use the PCI OHCI controller, this option is not necessary.
566 Enable support for the Samsung Exynos SOC's on-chip OHCI controller.
576 Enable support for the CNS3XXX SOC's on-chip OHCI controller.
577 It is needed for low-speed USB 1.0 device support.
588 bool "Octeon on-chip OHCI support (DEPRECATED)"
598 Enable support for the Octeon II SOC's on-chip OHCI
599 controller. It is needed for low-speed USB 1.0 device
600 support. All CN6XXX based chips with USB are supported.
608 The Universal Host Controller Interface is a standard by Intel for
609 accessing the USB hardware in the PC (which is also called the USB
610 host controller). If your USB host controller conforms to this
615 133) and LEON/GRLIB SoCs with the GRUSBHC controller.
619 module will be called uhci-hcd.
634 tristate "Freescale QE USB Host Controller support"
639 This driver enables support for Freescale QE USB Host Controller
641 Full and Low Speed USB.
644 bool "Freescale QE USB Host Controller debug support"
651 tristate "Elan U132 Adapter Host Controller"
654 The U132 adapter is a USB to CardBus adapter specifically designed
655 for PC cards that contain an OHCI host controller. Typical PC cards
658 controller.
663 The driver consists of two modules, the "ftdi-elan" module is a
664 USB client driver that interfaces to the FTDI chip within ELAN's
665 USB-to-PCMCIA adapter, and this "u132-hcd" module is a USB host
666 controller driver that talks to the OHCI controller within the
669 This driver has been tested with a CardBus OHCI USB adapter, and
670 worked with a USB PEN Drive inserted into the first USB port of
681 The SL811HS is a single-port USB controller that supports either
683 board has this chip, and you want to use it as a host controller.
687 module will be called sl811-hcd.
704 REX-CFU1U CF card (often used with PDAs). If unsure, say N.
713 The R8A66597 is a USB 2.0 host and peripheral controller.
716 to use it as a host controller. If unsure, say N.
719 module will be called r8a66597-hcd.
725 The Renesas USBHS is a USB 2.0 host and peripheral controller.
728 to use it as a host controller. If unsure, say N.
731 module will be called renesas-usbhs.
734 tristate "BCMA usb host driver"
739 Enable support for the EHCI and OCHI host controller on an bcma bus.
746 tristate "SSB usb host driver"
751 Enable support for the EHCI and OCHI host controller on an bcma bus.
761 supported by the host controller drivers.
763 One such test mode is the Embedded High-speed Host Electrical Test
764 (EHSET) for EHCI host controller hardware, specifically the "Single
765 Step Set Feature" test. Typically this will be enabled for On-the-Go
766 or embedded hosts that need to undergo USB-IF compliance testing with
771 their USB hardware designs. It is not needed for normal use. If