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.
128 Enables support for XHCI, EHCI and OHCI host controllers
132 modules will be called ohci-platform.ko, ehci-brcm.ko and
133 xhci-plat-hcd.ko
139 tristate "EHCI HCD (USB 2.0) support"
142 The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0
147 EHCI controllers are packaged with "companion" host controllers (OHCI
149 will connect to EHCI if the device is high speed, otherwise they
150 connect to a companion controller. If you configure EHCI, you should
155 You may want to read <file:Documentation/usb/ehci.rst>.
158 module will be called ehci-hcd.
164 Some EHCI chips have vendor-specific extensions to integrate
169 This supports the EHCI implementation that's originally
186 (possibly due to "ENOSPC" or "-28" errors), say Y. Conversely, if
200 bool "Use Xilinx usb host EHCI controller core"
205 Xilinx xps USB host controller core is EHCI compliant and has
206 transaction translator built-in. It can be configured to either
211 tristate "Support for Freescale on-chip EHCI USB controller"
217 tristate "Support for Nuvoton NPCM on-chip EHCI USB controller"
221 Enables support for the on-chip EHCI controller on
225 tristate "EHCI support for OMAP3 and later chips"
230 Enables support for the on-chip EHCI controller on
234 tristate "Support for Marvell EBU on-chip EHCI USB controller"
238 Enables support for the on-chip EHCI controller on Marvell's
240 Armada 370. This is different from the EHCI implementation
241 on Marvell's mobile PXA and MMP SoC, see "EHCI support for
245 tristate "Support for ST SPEAr on-chip EHCI USB controller"
249 Enables support for the on-chip EHCI controller on
253 tristate "Support for ST STiHxxx on-chip EHCI USB controller"
258 Enable support for the on-chip EHCI controller found on
262 tristate "Support for Atmel on-chip EHCI USB controller"
266 Enables support for the on-chip EHCI controller on
281 found in NVIDIA Tegra SoCs. The controllers are EHCI compliant.
284 bool "EHCI support for PPC USB controller on OF platform bus"
292 bool "EHCI support for SuperH USB controller"
295 Enables support for the on-chip EHCI controller on the SuperH.
296 If you use the PCI EHCI controller, this option is not necessary.
299 tristate "EHCI support for Samsung S5P/Exynos SoC Series"
302 Enable support for the Samsung S5Pv210 and Exynos SOC's on-chip EHCI
306 tristate "EHCI support for Marvell PXA/MMP USB controller"
310 Enables support for Marvell (including PXA and MMP series) on-chip
312 only be EHCI host. OTG is controller that can switch to host mode.
313 Note that this driver will not work on Marvell's other EHCI
314 controller used by the EBU-type SoCs including Orion, Kirkwood,
316 on-chip EHCI USB controller" for those.
326 will be called octeon-hcd.
329 tristate "Generic EHCI driver for a platform device"
331 Adds an EHCI host driver for a generic platform device, which
337 bool "Octeon on-chip EHCI support (DEPRECATED)"
345 Enable support for the Octeon II SOC's on-chip EHCI
346 controller. It is needed for high-speed (480Mbit/sec)
363 module will be called oxu210hp-hcd.
375 module will be called isp116x-hcd.
387 module will be called isp1362-hcd.
390 tristate "MAX3421 HCD (USB-over-SPI) support"
393 The Maxim MAX3421E chip supports standard USB 2.0-compliant
394 full-speed devices either in host or peripheral mode. This
395 driver supports the host-mode of the MAX3421E only.
398 be called max3421-hcd.
407 say Y. On most non-x86 systems, and on x86 hardware that's not using a
410 based system where you're not sure, the "lspci -v" entry will list the
411 right "prog-if" for your USB controller(s): EHCI, OHCI, or UHCI.
414 module will be called ohci-hcd.
426 tristate "Support for ST SPEAr on-chip OHCI USB controller"
430 Enables support for the on-chip OHCI controller on
434 tristate "Support for ST STiHxxx on-chip OHCI USB controller"
439 Enable support for the on-chip OHCI controller found on
447 Enables support for the on-chip OHCI controller on
451 tristate "Support for LPC on-chip OHCI USB controller"
457 Enables support for the on-chip OHCI controller on
461 tristate "Support for PXA27X/PXA3XX on-chip OHCI USB controller"
465 Enables support for the on-chip OHCI controller on
469 tristate "Support for Atmel on-chip OHCI USB controller"
473 Enables support for the on-chip OHCI controller on
485 Enables support for the on-chip OHCI controller on
505 Enables support for big-endian USB controllers present on the
513 Enables support for little-endian USB controllers present on the
522 tristate "OHCI support for PCI-bus USB controllers"
527 Enables support for PCI-bus plug-in USB controller cards.
551 Enable support for the Samsung S5Pv210 and Exynos SOC's on-chip OHCI
555 tristate "Generic OHCI driver for a platform device"
557 Adds an OHCI host driver for a generic platform device, which
563 bool "Octeon on-chip OHCI support (DEPRECATED)"
573 Enable support for the Octeon II SOC's on-chip OHCI
574 controller. It is needed for low-speed USB 1.0 device
594 module will be called uhci-hcd.
629 The SL811HS is a single-port USB controller that supports either
635 module will be called sl811-hcd.
652 REX-CFU1U CF card (often used with PDAs). If unsure, say N.
667 module will be called r8a66597-hcd.
679 module will be called renesas-usbhs.
687 Enable support for the EHCI and OCHI host controller on an bcma bus.
689 for ehci and ohci.
699 Enable support for the EHCI and OCHI host controller on an bcma bus.
701 for ehci and ohci.
711 One such test mode is the Embedded High-speed Host Electrical Test
712 (EHSET) for EHCI host controller hardware, specifically the "Single
713 Step Set Feature" test. Typically this will be enabled for On-the-Go
714 or embedded hosts that need to undergo USB-IF compliance testing with
730 Only needed if the kernel is running in a Xen guest and generic