1 # Host-side USB depends on having a host controller
2 # NOTE: dummy_hcd is always an option, but it's ignored here ...
3 # NOTE: SL-811 option should be board-specific ...
4 config USB_ARCH_HAS_HCD
6 default y if USB_ARCH_HAS_OHCI
7 default y if ARM # SL-811
10 # many non-PCI hcds implement OHCI
11 config USB_ARCH_HAS_OHCI
14 default y if ARCH_OMAP
15 default y if ARCH_LH7A404
20 # USB Host Controller Drivers
22 comment "USB Host Controller Drivers"
26 tristate "EHCI HCD (USB 2.0) support"
29 The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0
30 "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware.
31 If your USB host controller supports USB 2.0, you will likely want to
32 configure this Host Controller Driver. At this writing, the primary
33 implementation of EHCI is a chip from NEC, widely available in add-on
34 PCI cards, but implementations are in the works from other vendors
35 including Intel and Philips. Motherboard support is appearing.
37 EHCI controllers are packaged with "companion" host controllers (OHCI
38 or UHCI) to handle USB 1.1 devices connected to root hub ports. Ports
39 will connect to EHCI if it the device is high speed, otherwise they
40 connect to a companion controller. If you configure EHCI, you should
41 probably configure the OHCI (for NEC and some other vendors) USB Host
42 Controller Driver or UHCI (for Via motherboards) Host Controller
45 You may want to read <file:Documentation/usb/ehci.txt>.
47 To compile this driver as a module, choose M here: the
48 module will be called ehci-hcd.
50 config USB_EHCI_SPLIT_ISO
51 bool "Full speed ISO transactions (EXPERIMENTAL)"
52 depends on USB_EHCI_HCD && EXPERIMENTAL
55 This code is new and hasn't been used with many different
56 EHCI or USB 2.0 transaction translator implementations.
57 It should work for ISO-OUT transfers, like audio.
59 config USB_EHCI_ROOT_HUB_TT
60 bool "Root Hub Transaction Translators (EXPERIMENTAL)"
61 depends on USB_EHCI_HCD && EXPERIMENTAL
63 Some EHCI chips have vendor-specific extensions to integrate
64 transaction translators, so that no OHCI or UHCI companion
65 controller is needed. It's safe to say "y" even if your
66 controller doesn't support this feature.
68 This supports the EHCI implementation from ARC International.
71 tristate "OHCI HCD support"
72 depends on USB && USB_ARCH_HAS_OHCI
73 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3
75 The Open Host Controller Interface (OHCI) is a standard for accessing
76 USB 1.1 host controller hardware. It does more in hardware than Intel's
77 UHCI specification. If your USB host controller follows the OHCI spec,
78 say Y. On most non-x86 systems, and on x86 hardware that's not using a
79 USB controller from Intel or VIA, this is appropriate. If your host
80 controller doesn't use PCI, this is probably appropriate. For a PCI
81 based system where you're not sure, the "lspci -v" entry will list the
82 right "prog-if" for your USB controller(s): EHCI, OHCI, or UHCI.
84 To compile this driver as a module, choose M here: the
85 module will be called ohci-hcd.
88 tristate "UHCI HCD (most Intel and VIA) support"
91 The Universal Host Controller Interface is a standard by Intel for
92 accessing the USB hardware in the PC (which is also called the USB
93 host controller). If your USB host controller conforms to this
94 standard, you may want to say Y, but see below. All recent boards
95 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
96 i810, i820) conform to this standard. Also all VIA PCI chipsets
97 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
98 133). If unsure, say Y.
100 To compile this driver as a module, choose M here: the
101 module will be called uhci-hcd.
104 tristate "SL811HS HCD support"
108 The SL811HS is a single-port USB controller that supports either
109 host side or peripheral side roles. Enable this option if your
110 board has this chip, and you want to use it as a host controller.
113 To compile this driver as a module, choose M here: the
114 module will be called sl811-hcd.