xref: /linux/drivers/usb/host/Kconfig (revision 367b8112fe2ea5c39a7bb4d263dcdd9b612fae18)
1#
2# USB Host Controller Drivers
3#
4comment "USB Host Controller Drivers"
5	depends on USB
6
7config USB_C67X00_HCD
8	tristate "Cypress C67x00 HCD support"
9	depends on USB
10	help
11	  The Cypress C67x00 (EZ-Host/EZ-OTG) chips are dual-role
12	  host/peripheral/OTG USB controllers.
13
14	  Enable this option to support this chip in host controller mode.
15	  If unsure, say N.
16
17	  To compile this driver as a module, choose M here: the
18	  module will be called c67x00.
19
20config USB_EHCI_HCD
21	tristate "EHCI HCD (USB 2.0) support"
22	depends on USB && USB_ARCH_HAS_EHCI
23	---help---
24	  The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0
25	  "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware.
26	  If your USB host controller supports USB 2.0, you will likely want to
27	  configure this Host Controller Driver.  At the time of this writing,
28	  the primary implementation of EHCI is a chip from NEC, widely available
29	  in add-on PCI cards, but implementations are in the works from other
30	  vendors including Intel and Philips.  Motherboard support is appearing.
31
32	  EHCI controllers are packaged with "companion" host controllers (OHCI
33	  or UHCI) to handle USB 1.1 devices connected to root hub ports.  Ports
34	  will connect to EHCI if the device is high speed, otherwise they
35	  connect to a companion controller.  If you configure EHCI, you should
36	  probably configure the OHCI (for NEC and some other vendors) USB Host
37	  Controller Driver or UHCI (for Via motherboards) Host Controller
38	  Driver too.
39
40	  You may want to read <file:Documentation/usb/ehci.txt>.
41
42	  To compile this driver as a module, choose M here: the
43	  module will be called ehci-hcd.
44
45config USB_EHCI_ROOT_HUB_TT
46	bool "Root Hub Transaction Translators"
47	depends on USB_EHCI_HCD
48	---help---
49	  Some EHCI chips have vendor-specific extensions to integrate
50	  transaction translators, so that no OHCI or UHCI companion
51	  controller is needed.  It's safe to say "y" even if your
52	  controller doesn't support this feature.
53
54	  This supports the EHCI implementation that's originally
55	  from ARC, and has since changed hands a few times.
56
57config USB_EHCI_TT_NEWSCHED
58	bool "Improved Transaction Translator scheduling (EXPERIMENTAL)"
59	depends on USB_EHCI_HCD && EXPERIMENTAL
60	---help---
61	  This changes the periodic scheduling code to fill more of the low
62	  and full speed bandwidth available from the Transaction Translator
63	  (TT) in USB 2.0 hubs.  Without this, only one transfer will be
64	  issued in each microframe, significantly reducing the number of
65	  periodic low/fullspeed transfers possible.
66
67	  If you have multiple periodic low/fullspeed devices connected to a
68	  highspeed USB hub which is connected to a highspeed USB Host
69	  Controller, and some of those devices will not work correctly
70	  (possibly due to "ENOSPC" or "-28" errors), say Y.
71
72	  If unsure, say N.
73
74config USB_EHCI_BIG_ENDIAN_MMIO
75	bool
76	depends on USB_EHCI_HCD && (PPC_CELLEB || PPC_PS3 || 440EPX || ARCH_IXP4XX)
77	default y
78
79config USB_EHCI_BIG_ENDIAN_DESC
80	bool
81	depends on USB_EHCI_HCD && (440EPX || ARCH_IXP4XX)
82	default y
83
84config USB_EHCI_FSL
85	bool "Support for Freescale on-chip EHCI USB controller"
86	depends on USB_EHCI_HCD && FSL_SOC
87	select USB_EHCI_ROOT_HUB_TT
88	---help---
89	  Variation of ARC USB block used in some Freescale chips.
90
91config USB_EHCI_HCD_PPC_OF
92	bool "EHCI support for PPC USB controller on OF platform bus"
93	depends on USB_EHCI_HCD && PPC_OF
94	default y
95	---help---
96	  Enables support for the USB controller present on the PowerPC
97	  OpenFirmware platform bus.
98
99config USB_ISP116X_HCD
100	tristate "ISP116X HCD support"
101	depends on USB
102	---help---
103	  The ISP1160 and ISP1161 chips are USB host controllers. Enable this
104	  option if your board has this chip. If unsure, say N.
105
106	  This driver does not support isochronous transfers.
107
108	  To compile this driver as a module, choose M here: the
109	  module will be called isp116x-hcd.
110
111config USB_ISP1760_HCD
112	tristate "ISP 1760 HCD support"
113	depends on USB && EXPERIMENTAL
114	---help---
115	  The ISP1760 chip is a USB 2.0 host controller.
116
117	  This driver does not support isochronous transfers or OTG.
118
119	  To compile this driver as a module, choose M here: the
120	  module will be called isp1760-hcd.
121
122config USB_ISP1760_PCI
123	bool "Support for the PCI bus"
124	depends on USB_ISP1760_HCD && PCI
125	---help---
126	  Enables support for the device present on the PCI bus.
127	  This should only be required if you happen to have the eval kit from
128	  NXP and you are going to test it.
129
130config USB_ISP1760_OF
131	bool "Support for the OF platform bus"
132	depends on USB_ISP1760_HCD && PPC_OF
133	---help---
134	  Enables support for the device present on the PowerPC
135	  OpenFirmware platform bus.
136
137config USB_OHCI_HCD
138	tristate "OHCI HCD support"
139	depends on USB && USB_ARCH_HAS_OHCI
140	select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3
141	---help---
142	  The Open Host Controller Interface (OHCI) is a standard for accessing
143	  USB 1.1 host controller hardware.  It does more in hardware than Intel's
144	  UHCI specification.  If your USB host controller follows the OHCI spec,
145	  say Y.  On most non-x86 systems, and on x86 hardware that's not using a
146	  USB controller from Intel or VIA, this is appropriate.  If your host
147	  controller doesn't use PCI, this is probably appropriate.  For a PCI
148	  based system where you're not sure, the "lspci -v" entry will list the
149	  right "prog-if" for your USB controller(s):  EHCI, OHCI, or UHCI.
150
151	  To compile this driver as a module, choose M here: the
152	  module will be called ohci-hcd.
153
154config USB_OHCI_HCD_PPC_SOC
155	bool "OHCI support for on-chip PPC USB controller"
156	depends on USB_OHCI_HCD && (STB03xxx || PPC_MPC52xx)
157	default y
158	select USB_OHCI_BIG_ENDIAN_DESC
159	select USB_OHCI_BIG_ENDIAN_MMIO
160	---help---
161	  Enables support for the USB controller on the MPC52xx or
162	  STB03xxx processor chip.  If unsure, say Y.
163
164config USB_OHCI_HCD_PPC_OF
165	bool "OHCI support for PPC USB controller on OF platform bus"
166	depends on USB_OHCI_HCD && PPC_OF
167	default y
168	---help---
169	  Enables support for the USB controller PowerPC present on the
170	  OpenFirmware platform bus.
171
172config USB_OHCI_HCD_PPC_OF_BE
173	bool "Support big endian HC"
174	depends on USB_OHCI_HCD_PPC_OF
175	default y
176	select USB_OHCI_BIG_ENDIAN_DESC
177	select USB_OHCI_BIG_ENDIAN_MMIO
178
179config USB_OHCI_HCD_PPC_OF_LE
180	bool "Support little endian HC"
181	depends on USB_OHCI_HCD_PPC_OF
182	default n
183	select USB_OHCI_LITTLE_ENDIAN
184
185config USB_OHCI_HCD_PCI
186	bool "OHCI support for PCI-bus USB controllers"
187	depends on USB_OHCI_HCD && PCI && (STB03xxx || PPC_MPC52xx || USB_OHCI_HCD_PPC_OF)
188	default y
189	select USB_OHCI_LITTLE_ENDIAN
190	---help---
191	  Enables support for PCI-bus plug-in USB controller cards.
192	  If unsure, say Y.
193
194config USB_OHCI_HCD_SSB
195	bool "OHCI support for Broadcom SSB OHCI core"
196	depends on USB_OHCI_HCD && (SSB = y || SSB = USB_OHCI_HCD) && EXPERIMENTAL
197	default n
198	---help---
199	  Support for the Sonics Silicon Backplane (SSB) attached
200	  Broadcom USB OHCI core.
201
202	  This device is present in some embedded devices with
203	  Broadcom based SSB bus.
204
205	  If unsure, say N.
206
207config USB_OHCI_BIG_ENDIAN_DESC
208	bool
209	depends on USB_OHCI_HCD
210	default n
211
212config USB_OHCI_BIG_ENDIAN_MMIO
213	bool
214	depends on USB_OHCI_HCD
215	default n
216
217config USB_OHCI_LITTLE_ENDIAN
218	bool
219	depends on USB_OHCI_HCD
220	default n if STB03xxx || PPC_MPC52xx
221	default y
222
223config USB_UHCI_HCD
224	tristate "UHCI HCD (most Intel and VIA) support"
225	depends on USB && PCI
226	---help---
227	  The Universal Host Controller Interface is a standard by Intel for
228	  accessing the USB hardware in the PC (which is also called the USB
229	  host controller). If your USB host controller conforms to this
230	  standard, you may want to say Y, but see below. All recent boards
231	  with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
232	  i810, i820) conform to this standard. Also all VIA PCI chipsets
233	  (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
234	  133). If unsure, say Y.
235
236	  To compile this driver as a module, choose M here: the
237	  module will be called uhci-hcd.
238
239config USB_U132_HCD
240	tristate "Elan U132 Adapter Host Controller"
241	depends on USB && USB_FTDI_ELAN
242	default M
243	help
244	  The U132 adapter is a USB to CardBus adapter specifically designed
245	  for PC cards that contain an OHCI host controller. Typical PC cards
246	  are the Orange Mobile 3G Option GlobeTrotter Fusion card. The U132
247	  adapter will *NOT* work with PC cards that do not contain an OHCI
248	  controller.
249
250	  For those PC cards that contain multiple OHCI controllers only the
251	  first one is used.
252
253	  The driver consists of two modules, the "ftdi-elan" module is a
254	  USB client driver that interfaces to the FTDI chip within ELAN's
255	  USB-to-PCMCIA adapter, and this "u132-hcd" module is a USB host
256	  controller driver that talks to the OHCI controller within the
257	  CardBus cards that are inserted in the U132 adapter.
258
259	  This driver has been tested with a CardBus OHCI USB adapter, and
260	  worked with a USB PEN Drive inserted into the first USB port of
261	  the PCCARD. A rather pointless thing to do, but useful for testing.
262
263	  It is safe to say M here.
264
265	  See also <http://www.elandigitalsystems.com/support/ufaq/u132linux.php>
266
267config USB_SL811_HCD
268	tristate "SL811HS HCD support"
269	depends on USB
270	help
271	  The SL811HS is a single-port USB controller that supports either
272	  host side or peripheral side roles.  Enable this option if your
273	  board has this chip, and you want to use it as a host controller.
274	  If unsure, say N.
275
276	  To compile this driver as a module, choose M here: the
277	  module will be called sl811-hcd.
278
279config USB_SL811_CS
280	tristate "CF/PCMCIA support for SL811HS HCD"
281	depends on USB_SL811_HCD && PCMCIA
282	help
283	  Wraps a PCMCIA driver around the SL811HS HCD, supporting the RATOC
284	  REX-CFU1U CF card (often used with PDAs).  If unsure, say N.
285
286	  To compile this driver as a module, choose M here: the
287	  module will be called "sl811_cs".
288
289config USB_R8A66597_HCD
290	tristate "R8A66597 HCD support"
291	depends on USB
292	help
293	  The R8A66597 is a USB 2.0 host and peripheral controller.
294
295	  Enable this option if your board has this chip, and you want
296	  to use it as a host controller.  If unsure, say N.
297
298	  To compile this driver as a module, choose M here: the
299	  module will be called r8a66597-hcd.
300
301config SUPERH_ON_CHIP_R8A66597
302	boolean "Enable SuperH on-chip R8A66597 USB"
303	depends on USB_R8A66597_HCD && (CPU_SUBTYPE_SH7366 || CPU_SUBTYPE_SH7723)
304	help
305	   This driver enables support for the on-chip R8A66597 in the
306	   SH7366 and SH7723 processors.
307
308config USB_WHCI_HCD
309	tristate "Wireless USB Host Controller Interface (WHCI) driver (EXPERIMENTAL)"
310	depends on EXPERIMENTAL
311	depends on PCI && USB
312	select USB_WUSB
313	select UWB_WHCI
314	help
315	  A driver for PCI-based Wireless USB Host Controllers that are
316	  compliant with the WHCI specification.
317
318	  To compile this driver a module, choose M here: the module
319	  will be called "whci-hcd".
320
321config USB_HWA_HCD
322	tristate "Host Wire Adapter (HWA) driver (EXPERIMENTAL)"
323	depends on EXPERIMENTAL
324	depends on USB
325	select USB_WUSB
326	select UWB_HWA
327	help
328	  This driver enables you to connect Wireless USB devices to
329	  your system using a Host Wire Adaptor USB dongle. This is an
330	  UWB Radio Controller and WUSB Host Controller connected to
331	  your machine via USB (specified in WUSB1.0).
332
333	  To compile this driver a module, choose M here: the module
334	  will be called "hwa-hc".
335