Lines Matching +full:generic +full:- +full:ehci
1 # SPDX-License-Identifier: GPL-2.0
11 The Cypress C67x00 (EZ-Host/EZ-OTG) chips are dual-role
28 module will be called xhci-hcd.
55 tristate "Generic xHCI driver for a platform device"
57 Adds an xHCI host driver for a generic platform device, which
90 tristate "xHCI support for Renesas R-Car SoCs"
96 found in Renesas R-Car ARM SoCs.
137 Enables support for XHCI, EHCI and OHCI host controllers
141 modules will be called ohci-platform.ko, ehci-brcm.ko and
142 xhci-plat-hcd.ko
148 tristate "EHCI HCD (USB 2.0) support"
151 The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0
156 EHCI controllers are packaged with "companion" host controllers (OHCI
158 will connect to EHCI if the device is high speed, otherwise they
159 connect to a companion controller. If you configure EHCI, you should
164 You may want to read <file:Documentation/usb/ehci.rst>.
167 module will be called ehci-hcd.
173 Some EHCI chips have vendor-specific extensions to integrate
178 This supports the EHCI implementation that's originally
195 (possibly due to "ENOSPC" or "-28" errors), say Y. Conversely, if
209 bool "Use Xilinx usb host EHCI controller core"
214 Xilinx xps USB host controller core is EHCI compliant and has
215 transaction translator built-in. It can be configured to either
220 tristate "Support for Freescale on-chip EHCI USB controller"
226 tristate "Support for Nuvoton NPCM on-chip EHCI USB controller"
230 Enables support for the on-chip EHCI controller on
234 tristate "EHCI support for OMAP3 and later chips"
239 Enables support for the on-chip EHCI controller on
243 tristate "Support for Marvell EBU on-chip EHCI USB controller"
247 Enables support for the on-chip EHCI controller on Marvell's
249 Armada 370. This is different from the EHCI implementation
250 on Marvell's mobile PXA and MMP SoC, see "EHCI support for
254 tristate "Support for ST SPEAr on-chip EHCI USB controller"
258 Enables support for the on-chip EHCI controller on
262 tristate "Support for ST STiHxxx on-chip EHCI USB controller"
267 Enable support for the on-chip EHCI controller found on
271 tristate "Support for Atmel on-chip EHCI USB controller"
275 Enables support for the on-chip EHCI controller on
290 found in NVIDIA Tegra SoCs. The controllers are EHCI compliant.
293 bool "EHCI support for PPC USB controller on OF platform bus"
301 bool "EHCI support for SuperH USB controller"
304 Enables support for the on-chip EHCI controller on the SuperH.
305 If you use the PCI EHCI controller, this option is not necessary.
308 tristate "EHCI support for Samsung S5P/Exynos SoC Series"
311 Enable support for the Samsung S5Pv210 and Exynos SOC's on-chip EHCI
315 tristate "EHCI support for Marvell PXA/MMP USB controller"
319 Enables support for Marvell (including PXA and MMP series) on-chip
321 only be EHCI host. OTG is controller that can switch to host mode.
322 Note that this driver will not work on Marvell's other EHCI
323 controller used by the EBU-type SoCs including Orion, Kirkwood,
325 on-chip EHCI USB controller" for those.
335 will be called octeon-hcd.
338 tristate "Generic EHCI driver for a platform device"
340 Adds an EHCI host driver for a generic platform device, which
346 bool "Octeon on-chip EHCI support (DEPRECATED)"
354 Enable support for the Octeon II SOC's on-chip EHCI
355 controller. It is needed for high-speed (480Mbit/sec)
372 module will be called oxu210hp-hcd.
384 module will be called isp116x-hcd.
396 module will be called isp1362-hcd.
399 tristate "MAX3421 HCD (USB-over-SPI) support"
402 The Maxim MAX3421E chip supports standard USB 2.0-compliant
403 full-speed devices either in host or peripheral mode. This
404 driver supports the host-mode of the MAX3421E only.
407 be called max3421-hcd.
416 say Y. On most non-x86 systems, and on x86 hardware that's not using a
419 based system where you're not sure, the "lspci -v" entry will list the
420 right "prog-if" for your USB controller(s): EHCI, OHCI, or UHCI.
423 module will be called ohci-hcd.
435 tristate "Support for ST SPEAr on-chip OHCI USB controller"
439 Enables support for the on-chip OHCI controller on
443 tristate "Support for ST STiHxxx on-chip OHCI USB controller"
448 Enable support for the on-chip OHCI controller found on
456 Enables support for the on-chip OHCI controller on
460 tristate "Support for LPC on-chip OHCI USB controller"
466 Enables support for the on-chip OHCI controller on
470 tristate "Support for PXA27X/PXA3XX on-chip OHCI USB controller"
474 Enables support for the on-chip OHCI controller on
478 tristate "Support for Atmel on-chip OHCI USB controller"
482 Enables support for the on-chip OHCI controller on
494 Enables support for the on-chip OHCI controller on
514 Enables support for big-endian USB controllers present on the
522 Enables support for little-endian USB controllers present on the
531 tristate "OHCI support for PCI-bus USB controllers"
536 Enables support for PCI-bus plug-in USB controller cards.
560 Enable support for the Samsung S5Pv210 and Exynos SOC's on-chip OHCI
564 tristate "Generic OHCI driver for a platform device"
566 Adds an OHCI host driver for a generic platform device, which
572 bool "Octeon on-chip OHCI support (DEPRECATED)"
582 Enable support for the Octeon II SOC's on-chip OHCI
583 controller. It is needed for low-speed USB 1.0 device
603 module will be called uhci-hcd.
638 The SL811HS is a single-port USB controller that supports either
644 module will be called sl811-hcd.
661 REX-CFU1U CF card (often used with PDAs). If unsure, say N.
676 module will be called r8a66597-hcd.
688 module will be called renesas-usbhs.
696 Enable support for the EHCI and OCHI host controller on an bcma bus.
698 for ehci and ohci.
708 Enable support for the EHCI and OCHI host controller on an bcma bus.
710 for ehci and ohci.
720 One such test mode is the Embedded High-speed Host Electrical Test
721 (EHSET) for EHCI host controller hardware, specifically the "Single
722 Step Set Feature" test. Typically this will be enabled for On-the-Go
723 or embedded hosts that need to undergo USB-IF compliance testing with
739 Only needed if the kernel is running in a Xen guest and generic