1# 2# USB Host Controller Drivers 3# 4comment "USB Host Controller Drivers" 5 depends on USB 6 7config USB_EHCI_HCD 8 tristate "EHCI HCD (USB 2.0) support" 9 depends on USB && USB_ARCH_HAS_EHCI 10 ---help--- 11 The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0 12 "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware. 13 If your USB host controller supports USB 2.0, you will likely want to 14 configure this Host Controller Driver. At the time of this writing, 15 the primary implementation of EHCI is a chip from NEC, widely available 16 in add-on PCI cards, but implementations are in the works from other 17 vendors including Intel and Philips. Motherboard support is appearing. 18 19 EHCI controllers are packaged with "companion" host controllers (OHCI 20 or UHCI) to handle USB 1.1 devices connected to root hub ports. Ports 21 will connect to EHCI if the device is high speed, otherwise they 22 connect to a companion controller. If you configure EHCI, you should 23 probably configure the OHCI (for NEC and some other vendors) USB Host 24 Controller Driver or UHCI (for Via motherboards) Host Controller 25 Driver too. 26 27 You may want to read <file:Documentation/usb/ehci.txt>. 28 29 To compile this driver as a module, choose M here: the 30 module will be called ehci-hcd. 31 32config USB_EHCI_SPLIT_ISO 33 bool "Full speed ISO transactions (EXPERIMENTAL)" 34 depends on USB_EHCI_HCD && EXPERIMENTAL 35 default n 36 ---help--- 37 This code is new and hasn't been used with many different 38 EHCI or USB 2.0 transaction translator implementations. 39 It should work for ISO-OUT transfers, like audio. 40 41config USB_EHCI_ROOT_HUB_TT 42 bool "Root Hub Transaction Translators (EXPERIMENTAL)" 43 depends on USB_EHCI_HCD && EXPERIMENTAL 44 ---help--- 45 Some EHCI chips have vendor-specific extensions to integrate 46 transaction translators, so that no OHCI or UHCI companion 47 controller is needed. It's safe to say "y" even if your 48 controller doesn't support this feature. 49 50 This supports the EHCI implementation that's originally 51 from ARC, and has since changed hands a few times. 52 53config USB_EHCI_TT_NEWSCHED 54 bool "Improved Transaction Translator scheduling (EXPERIMENTAL)" 55 depends on USB_EHCI_HCD && EXPERIMENTAL 56 ---help--- 57 This changes the periodic scheduling code to fill more of the low 58 and full speed bandwidth available from the Transaction Translator 59 (TT) in USB 2.0 hubs. Without this, only one transfer will be 60 issued in each microframe, significantly reducing the number of 61 periodic low/fullspeed transfers possible. 62 63 If you have multiple periodic low/fullspeed devices connected to a 64 highspeed USB hub which is connected to a highspeed USB Host 65 Controller, and some of those devices will not work correctly 66 (possibly due to "ENOSPC" or "-28" errors), say Y. 67 68 If unsure, say N. 69 70config USB_ISP116X_HCD 71 tristate "ISP116X HCD support" 72 depends on USB 73 ---help--- 74 The ISP1160 and ISP1161 chips are USB host controllers. Enable this 75 option if your board has this chip. If unsure, say N. 76 77 This driver does not support isochronous transfers. 78 79 To compile this driver as a module, choose M here: the 80 module will be called isp116x-hcd. 81 82config USB_OHCI_HCD 83 tristate "OHCI HCD support" 84 depends on USB && USB_ARCH_HAS_OHCI 85 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 86 select I2C if ARCH_PNX4008 87 ---help--- 88 The Open Host Controller Interface (OHCI) is a standard for accessing 89 USB 1.1 host controller hardware. It does more in hardware than Intel's 90 UHCI specification. If your USB host controller follows the OHCI spec, 91 say Y. On most non-x86 systems, and on x86 hardware that's not using a 92 USB controller from Intel or VIA, this is appropriate. If your host 93 controller doesn't use PCI, this is probably appropriate. For a PCI 94 based system where you're not sure, the "lspci -v" entry will list the 95 right "prog-if" for your USB controller(s): EHCI, OHCI, or UHCI. 96 97 To compile this driver as a module, choose M here: the 98 module will be called ohci-hcd. 99 100config USB_OHCI_HCD_PPC_SOC 101 bool "OHCI support for on-chip PPC USB controller" 102 depends on USB_OHCI_HCD && (STB03xxx || PPC_MPC52xx) 103 default y 104 select USB_OHCI_BIG_ENDIAN 105 ---help--- 106 Enables support for the USB controller on the MPC52xx or 107 STB03xxx processor chip. If unsure, say Y. 108 109config USB_OHCI_HCD_PCI 110 bool "OHCI support for PCI-bus USB controllers" 111 depends on USB_OHCI_HCD && PCI && (STB03xxx || PPC_MPC52xx) 112 default y 113 select USB_OHCI_LITTLE_ENDIAN 114 ---help--- 115 Enables support for PCI-bus plug-in USB controller cards. 116 If unsure, say Y. 117 118config USB_OHCI_BIG_ENDIAN 119 bool 120 depends on USB_OHCI_HCD 121 default n 122 123config USB_OHCI_LITTLE_ENDIAN 124 bool 125 depends on USB_OHCI_HCD 126 default n if STB03xxx || PPC_MPC52xx 127 default y 128 129config USB_UHCI_HCD 130 tristate "UHCI HCD (most Intel and VIA) support" 131 depends on USB && PCI 132 ---help--- 133 The Universal Host Controller Interface is a standard by Intel for 134 accessing the USB hardware in the PC (which is also called the USB 135 host controller). If your USB host controller conforms to this 136 standard, you may want to say Y, but see below. All recent boards 137 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX, 138 i810, i820) conform to this standard. Also all VIA PCI chipsets 139 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro 140 133). If unsure, say Y. 141 142 To compile this driver as a module, choose M here: the 143 module will be called uhci-hcd. 144 145config USB_U132_HCD 146 tristate "Elan U132 Adapter Host Controller" 147 depends on USB && USB_FTDI_ELAN 148 default M 149 help 150 The U132 adapter is a USB to CardBus adapter specifically designed 151 for PC cards that contain an OHCI host controller. Typical PC cards 152 are the Orange Mobile 3G Option GlobeTrotter Fusion card. The U132 153 adapter will *NOT* work with PC cards that do not contain an OHCI 154 controller. 155 156 For those PC cards that contain multiple OHCI controllers only the 157 first one is used. 158 159 The driver consists of two modules, the "ftdi-elan" module is a 160 USB client driver that interfaces to the FTDI chip within ELAN's 161 USB-to-PCMCIA adapter, and this "u132-hcd" module is a USB host 162 controller driver that talks to the OHCI controller within the 163 CardBus cards that are inserted in the U132 adapter. 164 165 This driver has been tested with a CardBus OHCI USB adapter, and 166 worked with a USB PEN Drive inserted into the first USB port of 167 the PCCARD. A rather pointless thing to do, but useful for testing. 168 169 It is safe to say M here. 170 171 See also <http://www.elandigitalsystems.com/support/ufaq/u132linux.php> 172 173config USB_SL811_HCD 174 tristate "SL811HS HCD support" 175 depends on USB 176 help 177 The SL811HS is a single-port USB controller that supports either 178 host side or peripheral side roles. Enable this option if your 179 board has this chip, and you want to use it as a host controller. 180 If unsure, say N. 181 182 To compile this driver as a module, choose M here: the 183 module will be called sl811-hcd. 184 185config USB_SL811_CS 186 tristate "CF/PCMCIA support for SL811HS HCD" 187 depends on USB_SL811_HCD && PCMCIA 188 help 189 Wraps a PCMCIA driver around the SL811HS HCD, supporting the RATOC 190 REX-CFU1U CF card (often used with PDAs). If unsure, say N. 191 192 To compile this driver as a module, choose M here: the 193 module will be called "sl811_cs". 194 195