blob: 271ca161d7ef0c77e87f02e9c10db94034391340 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# USB Gadget support on a system involves
3# (a) a peripheral controller, and
4# (b) the gadget driver using it.
5#
6# NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
7#
8# - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
9# - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
Matt LaPlantecab00892006-10-03 22:36:44 +020010# - Some systems have both kinds of controllers.
Linus Torvalds1da177e2005-04-16 15:20:36 -070011#
12# With help from a special transceiver and a "Mini-AB" jack, systems with
13# both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
14#
Linus Torvalds1da177e2005-04-16 15:20:36 -070015
Denis Chengb75be4a2008-01-24 16:36:31 +080016menuconfig USB_GADGET
17 tristate "USB Gadget Support"
Alan Stern86dc2432011-11-17 16:42:24 -050018 select NLS
Linus Torvalds1da177e2005-04-16 15:20:36 -070019 help
20 USB is a master/slave protocol, organized with one master
21 host (such as a PC) controlling up to 127 peripheral devices.
22 The USB hardware is asymmetric, which makes it easier to set up:
23 you can't connect a "to-the-host" connector to a peripheral.
24
25 Linux can run in the host, or in the peripheral. In both cases
26 you need a low level bus controller driver, and some software
27 talking to it. Peripheral controllers are often discrete silicon,
28 or are integrated with the CPU in a microcontroller. The more
Jules Villarde113f292006-08-22 22:40:15 +020029 familiar host side controllers have names like "EHCI", "OHCI",
Linus Torvalds1da177e2005-04-16 15:20:36 -070030 or "UHCI", and are usually integrated into southbridges on PC
31 motherboards.
32
33 Enable this configuration option if you want to run Linux inside
34 a USB peripheral device. Configure one hardware driver for your
35 peripheral/device side bus controller, and a "gadget driver" for
36 your peripheral protocol. (If you use modular gadget drivers,
37 you may configure more than one.)
38
39 If in doubt, say "N" and don't enable these drivers; most people
40 don't have this kind of hardware (except maybe inside Linux PDAs).
41
42 For more information, see <http://www.linux-usb.org/gadget> and
43 the kernel DocBook documentation for this API.
44
Denis Chengb75be4a2008-01-24 16:36:31 +080045if USB_GADGET
46
David Brownell70790f62007-07-01 17:35:28 -070047config USB_GADGET_DEBUG
Robert P. J. Dayafd0e0f2008-03-10 15:09:51 -040048 boolean "Debugging messages (DEVELOPMENT)"
David Brownell36e893d2008-09-12 09:39:06 -070049 depends on DEBUG_KERNEL
David Brownell70790f62007-07-01 17:35:28 -070050 help
51 Many controller and gadget drivers will print some debugging
52 messages if you use this option to ask for those messages.
53
54 Avoid enabling these messages, even if you're actively
55 debugging such a driver. Many drivers will emit so many
56 messages that the driver timings are affected, which will
57 either create new failure modes or remove the one you're
58 trying to track down. Never enable these messages for a
59 production build.
60
Linus Torvalds1da177e2005-04-16 15:20:36 -070061config USB_GADGET_DEBUG_FILES
Robert P. J. Dayafd0e0f2008-03-10 15:09:51 -040062 boolean "Debugging information files (DEVELOPMENT)"
David Brownell36e893d2008-09-12 09:39:06 -070063 depends on PROC_FS
Linus Torvalds1da177e2005-04-16 15:20:36 -070064 help
65 Some of the drivers in the "gadget" framework can expose
66 debugging information in files such as /proc/driver/udc
67 (for a peripheral controller). The information in these
68 files may help when you're troubleshooting or bringing up a
69 driver on a new board. Enable these files by choosing "Y"
70 here. If in doubt, or to conserve kernel memory, say "N".
71
Haavard Skinnemoen914a3f32007-10-10 02:29:43 -070072config USB_GADGET_DEBUG_FS
Robert P. J. Dayafd0e0f2008-03-10 15:09:51 -040073 boolean "Debugging information files in debugfs (DEVELOPMENT)"
David Brownell36e893d2008-09-12 09:39:06 -070074 depends on DEBUG_FS
Haavard Skinnemoen914a3f32007-10-10 02:29:43 -070075 help
76 Some of the drivers in the "gadget" framework can expose
77 debugging information in files under /sys/kernel/debug/.
78 The information in these files may help when you're
79 troubleshooting or bringing up a driver on a new board.
80 Enable these files by choosing "Y" here. If in doubt, or
81 to conserve kernel memory, say "N".
82
David Brownell36e893d2008-09-12 09:39:06 -070083config USB_GADGET_VBUS_DRAW
84 int "Maximum VBUS Power usage (2-500 mA)"
85 range 2 500
86 default 2
87 help
88 Some devices need to draw power from USB when they are
89 configured, perhaps to operate circuitry or to recharge
90 batteries. This is in addition to any local power supply,
91 such as an AC adapter or batteries.
92
93 Enter the maximum power your device draws through USB, in
94 milliAmperes. The permitted range of values is 2 - 500 mA;
95 0 mA would be legal, but can make some hosts misbehave.
96
97 This value will be used except for system-specific gadget
98 drivers that have more specific information.
99
Per Forlin6532c7f2011-08-19 21:21:27 +0200100config USB_GADGET_STORAGE_NUM_BUFFERS
101 int "Number of storage pipeline buffers"
102 range 2 4
103 default 2
104 help
105 Usually 2 buffers are enough to establish a good buffering
106 pipeline. The number may be increased in order to compensate
107 for a bursty VFS behaviour. For instance there may be CPU wake up
108 latencies that makes the VFS to appear bursty in a system with
109 an CPU on-demand governor. Especially if DMA is doing IO to
110 offload the CPU. In this case the CPU will go into power
111 save often and spin up occasionally to move data within VFS.
112 If selecting USB_GADGET_DEBUG_FILES this value may be set by
113 a module parameter as well.
114 If unsure, say 2.
115
Linus Torvalds1da177e2005-04-16 15:20:36 -0700116#
117# USB Peripheral Controller Support
118#
David Brownella7a19fa2008-08-14 17:04:48 -0700119# The order here is alphabetical, except that integrated controllers go
120# before discrete ones so they will be the initial/default value:
121# - integrated/SOC controllers first
122# - licensed IP used in both SOC and discrete versions
123# - discrete ones (including all PCI-only controllers)
124# - debug/dummy gadget+hcd is last.
125#
Alexander Shishkined6c6f42012-05-08 23:29:00 +0300126menu "USB Peripheral Controller"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700127
David Brownella7a19fa2008-08-14 17:04:48 -0700128#
129# Integrated controllers
130#
131
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300132config USB_AT91
133 tristate "Atmel AT91 USB Device Port"
Jean-Christophe PLAGNIOL-VILLARDd1494a32012-01-28 22:35:36 +0800134 depends on ARCH_AT91
Thomas Dahlmann55d402d2007-07-16 21:40:54 -0700135 help
David Brownella7a19fa2008-08-14 17:04:48 -0700136 Many Atmel AT91 processors (such as the AT91RM2000) have a
137 full speed USB Device Port with support for five configurable
138 endpoints (plus endpoint zero).
Thomas Dahlmann55d402d2007-07-16 21:40:54 -0700139
140 Say "y" to link the driver statically, or "m" to build a
David Brownella7a19fa2008-08-14 17:04:48 -0700141 dynamically linked module called "at91_udc" and force all
Thomas Dahlmann55d402d2007-07-16 21:40:54 -0700142 gadget drivers to also be dynamically linked.
143
Roland Stigge24a28e42012-04-29 16:47:05 +0200144config USB_LPC32XX
145 tristate "LPC32XX USB Peripheral Controller"
146 depends on ARCH_LPC32XX
147 select USB_ISP1301
148 help
149 This option selects the USB device controller in the LPC32xx SoC.
150
151 Say "y" to link the driver statically, or "m" to build a
152 dynamically linked module called "lpc32xx_udc" and force all
153 gadget drivers to also be dynamically linked.
154
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300155config USB_ATMEL_USBA
156 tristate "Atmel USBA"
Haavard Skinnemoen914a3f32007-10-10 02:29:43 -0700157 select USB_GADGET_DUALSPEED
Jean-Christophe PLAGNIOL-VILLARD9918cea2012-01-26 14:07:09 +0100158 depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
Haavard Skinnemoen914a3f32007-10-10 02:29:43 -0700159 help
160 USBA is the integrated high-speed USB Device controller on
Nicolas Ferreba45ca42008-04-08 13:59:18 +0100161 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
Haavard Skinnemoen914a3f32007-10-10 02:29:43 -0700162
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300163config USB_FSL_USB2
164 tristate "Freescale Highspeed USB DR Peripheral Controller"
Guennadi Liakhovetski54e4026b2009-04-15 14:25:33 +0200165 depends on FSL_SOC || ARCH_MXC
Li Yangb5048822007-04-23 10:54:25 -0700166 select USB_GADGET_DUALSPEED
Marc Kleine-Budde018b97d2010-10-29 11:04:49 +0200167 select USB_FSL_MPH_DR_OF if OF
Li Yangb5048822007-04-23 10:54:25 -0700168 help
Fabio Estevam00c16f92012-04-09 17:14:16 -0300169 Some of Freescale PowerPC and i.MX processors have a High Speed
Li Yangb5048822007-04-23 10:54:25 -0700170 Dual-Role(DR) USB controller, which supports device mode.
171
172 The number of programmable endpoints is different through
173 SOC revisions.
174
175 Say "y" to link the driver statically, or "m" to build a
176 dynamically linked module called "fsl_usb2_udc" and force
177 all gadget drivers to also be dynamically linked.
178
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300179config USB_FUSB300
180 tristate "Faraday FUSB300 USB Peripheral Controller"
Sebastian Andrzej Siewiorac173172011-07-05 16:39:48 +0300181 depends on !PHYS_ADDR_T_64BIT
Yuan-Hsin Chen0fe6f1d2011-01-18 14:49:28 +0800182 select USB_GADGET_DUALSPEED
183 help
184 Faraday usb device controller FUSB300 driver
185
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300186config USB_OMAP
187 tristate "OMAP USB Device Controller"
Tony Lindgrenb924b202012-06-04 00:56:15 -0700188 depends on ARCH_OMAP1
Tony Lindgrenf1c9e152008-09-04 16:25:14 -0700189 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
David Brownell54b9ed32009-02-11 22:31:12 -0800190 select USB_OTG_UTILS if ARCH_OMAP
Linus Torvalds1da177e2005-04-16 15:20:36 -0700191 help
192 Many Texas Instruments OMAP processors have flexible full
193 speed USB device controllers, with support for up to 30
194 endpoints (plus endpoint zero). This driver supports the
195 controller in the OMAP 1611, and should work with controllers
196 in other OMAP processors too, given minor tweaks.
197
198 Say "y" to link the driver statically, or "m" to build a
199 dynamically linked module called "omap_udc" and force all
200 gadget drivers to also be dynamically linked.
201
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300202config USB_PXA25X
203 tristate "PXA 25x or IXP 4xx"
David Brownella7a19fa2008-08-14 17:04:48 -0700204 depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
Russell King09963912009-10-21 13:20:32 +0100205 select USB_OTG_UTILS
David Brownella7a19fa2008-08-14 17:04:48 -0700206 help
207 Intel's PXA 25x series XScale ARM-5TE processors include
208 an integrated full speed USB 1.1 device controller. The
209 controller in the IXP 4xx series is register-compatible.
210
211 It has fifteen fixed-function endpoints, as well as endpoint
212 zero (for control transfers).
213
214 Say "y" to link the driver statically, or "m" to build a
215 dynamically linked module called "pxa25x_udc" and force all
216 gadget drivers to also be dynamically linked.
217
David Brownella7a19fa2008-08-14 17:04:48 -0700218# if there's only one gadget driver, using only two bulk endpoints,
219# don't waste memory for the other endpoints
220config USB_PXA25X_SMALL
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300221 depends on USB_PXA25X
David Brownella7a19fa2008-08-14 17:04:48 -0700222 bool
223 default n if USB_ETH_RNDIS
224 default y if USB_ZERO
225 default y if USB_ETH
226 default y if USB_G_SERIAL
227
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300228config USB_R8A66597
229 tristate "Renesas R8A66597 USB Peripheral Controller"
Yoshihiro Shimodac4144242009-08-19 04:59:39 +0000230 select USB_GADGET_DUALSPEED
231 help
232 R8A66597 is a discrete USB host and peripheral controller chip that
233 supports both full and high speed USB 2.0 data transfers.
234 It has nine configurable endpoints, and endpoint zero.
235
236 Say "y" to link the driver statically, or "m" to build a
237 dynamically linked module called "r8a66597_udc" and force all
238 gadget drivers to also be dynamically linked.
239
Kuninori Morimoto030ed1f2011-07-07 02:17:37 -0700240config USB_RENESAS_USBHS_UDC
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300241 tristate 'Renesas USBHS controller'
Kuninori Morimoto030ed1f2011-07-07 02:17:37 -0700242 depends on USB_RENESAS_USBHS
243 select USB_GADGET_DUALSPEED
Kuninori Morimoto2f983822011-04-05 11:40:54 +0900244 help
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300245 Renesas USBHS is a discrete USB host and peripheral controller chip
246 that supports both full and high speed USB 2.0 data transfers.
247 It has nine or more configurable endpoints, and endpoint zero.
Kuninori Morimoto2f983822011-04-05 11:40:54 +0900248
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300249 Say "y" to link the driver statically, or "m" to build a
250 dynamically linked module called "renesas_usbhs" and force all
251 gadget drivers to also be dynamically linked.
Kuninori Morimoto2f983822011-04-05 11:40:54 +0900252
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300253config USB_PXA27X
254 tristate "PXA 27x"
Robert Jarzmik9f5351b2009-04-21 20:34:44 -0700255 depends on ARCH_PXA && (PXA27x || PXA3xx)
Robert Jarzmik7fec3c22009-01-24 23:57:30 -0800256 select USB_OTG_UTILS
David Brownella7a19fa2008-08-14 17:04:48 -0700257 help
258 Intel's PXA 27x series XScale ARM v5TE processors include
259 an integrated full speed USB 1.1 device controller.
260
261 It has up to 23 endpoints, as well as endpoint zero (for
262 control transfers).
263
264 Say "y" to link the driver statically, or "m" to build a
265 dynamically linked module called "pxa27x_udc" and force all
266 gadget drivers to also be dynamically linked.
267
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300268config USB_S3C_HSOTG
269 tristate "S3C HS/OtG USB Device controller"
Ben Dooks5b7d70c2009-06-02 14:58:06 +0100270 depends on S3C_DEV_USB_HSOTG
Maurus Cuelenaere0287e432010-05-25 05:36:49 +0100271 select USB_GADGET_DUALSPEED
Ben Dooks5b7d70c2009-06-02 14:58:06 +0100272 help
273 The Samsung S3C64XX USB2.0 high-speed gadget controller
274 integrated into the S3C64XX series SoC.
275
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300276config USB_IMX
Sascha Hauer2e5a08a2011-08-24 08:41:11 +0200277 tristate "Freescale i.MX1 USB Peripheral Controller"
278 depends on ARCH_MXC
Paulius Zaleckasc03e7d42009-06-09 11:11:16 +0300279 help
Sascha Hauer2e5a08a2011-08-24 08:41:11 +0200280 Freescale's i.MX1 includes an integrated full speed
281 USB 1.1 device controller.
Paulius Zaleckasc03e7d42009-06-09 11:11:16 +0300282
283 It has Six fixed-function endpoints, as well as endpoint
284 zero (for control transfers).
285
286 Say "y" to link the driver statically, or "m" to build a
287 dynamically linked module called "imx_udc" and force all
288 gadget drivers to also be dynamically linked.
289
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300290config USB_S3C2410
291 tristate "S3C2410 USB Device Controller"
Kukjin Kimb130d5c2012-02-03 14:29:23 +0900292 depends on ARCH_S3C24XX
Arnaud Patard3fc154b2007-06-06 21:05:49 -0700293 help
294 Samsung's S3C2410 is an ARM-4 processor with an integrated
295 full speed USB 1.1 device controller. It has 4 configurable
296 endpoints, as well as endpoint zero (for control transfers).
297
298 This driver has been tested on the S3C2410, S3C2412, and
299 S3C2440 processors.
300
Arnaud Patard3fc154b2007-06-06 21:05:49 -0700301config USB_S3C2410_DEBUG
302 boolean "S3C2410 udc debug messages"
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300303 depends on USB_S3C2410
Arnaud Patard3fc154b2007-06-06 21:05:49 -0700304
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300305config USB_S3C_HSUDC
306 tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
Kukjin Kimb130d5c2012-02-03 14:29:23 +0900307 depends on ARCH_S3C24XX
Thomas Abrahama9df3042011-05-07 22:28:04 +0200308 select USB_GADGET_DUALSPEED
309 help
310 Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
311 integrated with dual speed USB 2.0 device controller. It has
312 8 endpoints, as well as endpoint zero.
313
314 This driver has been tested on S3C2416 and S3C2450 processors.
315
Neil Zhang5e6c86b2011-12-20 13:20:21 +0800316config USB_MV_UDC
317 tristate "Marvell USB2.0 Device Controller"
cxie4e7cddda2010-11-30 13:35:15 +0800318 select USB_GADGET_DUALSPEED
319 help
Neil Zhang5e6c86b2011-12-20 13:20:21 +0800320 Marvell Socs (including PXA and MMP series) include a high speed
321 USB2.0 OTG controller, which can be configured as high speed or
322 full speed USB peripheral.
Felipe Balbi72246da2011-08-19 18:10:58 +0300323
David Brownella7a19fa2008-08-14 17:04:48 -0700324#
325# Controllers available in both integrated and discrete versions
326#
327
328# musb builds in ../musb along with host support
329config USB_GADGET_MUSB_HDRC
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300330 tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
Rabin Vincentb61ae342011-07-18 18:38:47 +0530331 depends on USB_MUSB_HDRC
David Brownella7a19fa2008-08-14 17:04:48 -0700332 select USB_GADGET_DUALSPEED
David Brownellbae4bd82006-01-22 10:32:37 -0800333 help
David Brownella7a19fa2008-08-14 17:04:48 -0700334 This OTG-capable silicon IP is used in dual designs including
Bryan Wu085ad402008-12-02 21:33:49 +0200335 the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
David Brownella7a19fa2008-08-14 17:04:48 -0700336
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300337config USB_M66592
338 tristate "Renesas M66592 USB Peripheral Controller"
David Brownella7a19fa2008-08-14 17:04:48 -0700339 select USB_GADGET_DUALSPEED
340 help
341 M66592 is a discrete USB peripheral controller chip that
342 supports both full and high speed USB 2.0 data transfers.
343 It has seven configurable endpoints, and endpoint zero.
David Brownellbae4bd82006-01-22 10:32:37 -0800344
345 Say "y" to link the driver statically, or "m" to build a
David Brownella7a19fa2008-08-14 17:04:48 -0700346 dynamically linked module called "m66592_udc" and force all
David Brownellbae4bd82006-01-22 10:32:37 -0800347 gadget drivers to also be dynamically linked.
348
David Brownella7a19fa2008-08-14 17:04:48 -0700349#
350# Controllers available only in discrete form (and all PCI controllers)
351#
352
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300353config USB_AMD5536UDC
354 tristate "AMD5536 UDC"
David Brownella7a19fa2008-08-14 17:04:48 -0700355 depends on PCI
356 select USB_GADGET_DUALSPEED
357 help
358 The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
359 It is a USB Highspeed DMA capable USB device controller. Beside ep0
360 it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
361 The UDC port supports OTG operation, and may be used as a host port
362 if it's not being used to implement peripheral or OTG roles.
363
364 Say "y" to link the driver statically, or "m" to build a
365 dynamically linked module called "amd5536udc" and force all
366 gadget drivers to also be dynamically linked.
367
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300368config USB_FSL_QE
369 tristate "Freescale QE/CPM USB Device Controller"
Li Yang3948f0e2008-09-02 19:58:10 +0800370 depends on FSL_SOC && (QUICC_ENGINE || CPM)
371 help
372 Some of Freescale PowerPC processors have a Full Speed
373 QE/CPM2 USB controller, which support device mode with 4
374 programmable endpoints. This driver supports the
375 controller in the MPC8360 and MPC8272, and should work with
376 controllers having QE or CPM2, given minor tweaks.
377
378 Set CONFIG_USB_GADGET to "m" to build this driver as a
Matt LaPlante692105b2009-01-26 11:12:25 +0100379 dynamically linked module called "fsl_qe_udc".
Li Yang3948f0e2008-09-02 19:58:10 +0800380
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300381config USB_NET2272
382 tristate "PLX NET2272"
Seth Levyceb80362011-06-06 19:42:44 -0400383 select USB_GADGET_DUALSPEED
384 help
385 PLX NET2272 is a USB peripheral controller which supports
386 both full and high speed USB 2.0 data transfers.
387
388 It has three configurable endpoints, as well as endpoint zero
389 (for control transfer).
390 Say "y" to link the driver statically, or "m" to build a
391 dynamically linked module called "net2272" and force all
392 gadget drivers to also be dynamically linked.
393
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300394config USB_NET2272_DMA
Seth Levyceb80362011-06-06 19:42:44 -0400395 boolean "Support external DMA controller"
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300396 depends on USB_NET2272
Seth Levyceb80362011-06-06 19:42:44 -0400397 help
398 The NET2272 part can optionally support an external DMA
399 controller, but your board has to have support in the
400 driver itself.
401
402 If unsure, say "N" here. The driver works fine in PIO mode.
403
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300404config USB_NET2280
405 tristate "NetChip 228x"
David Brownella7a19fa2008-08-14 17:04:48 -0700406 depends on PCI
407 select USB_GADGET_DUALSPEED
408 help
409 NetChip 2280 / 2282 is a PCI based USB peripheral controller which
410 supports both full and high speed USB 2.0 data transfers.
411
412 It has six configurable endpoints, as well as endpoint zero
413 (for control transfers) and several endpoints with dedicated
414 functions.
415
416 Say "y" to link the driver statically, or "m" to build a
417 dynamically linked module called "net2280" and force all
418 gadget drivers to also be dynamically linked.
419
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300420config USB_GOKU
421 tristate "Toshiba TC86C001 'Goku-S'"
David Brownella7a19fa2008-08-14 17:04:48 -0700422 depends on PCI
423 help
424 The Toshiba TC86C001 is a PCI device which includes controllers
425 for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
426
427 The device controller has three configurable (bulk or interrupt)
428 endpoints, plus endpoint zero (for control transfers).
429
430 Say "y" to link the driver statically, or "m" to build a
431 dynamically linked module called "goku_udc" and to force all
432 gadget drivers to also be dynamically linked.
433
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300434config USB_EG20T
Tomoya MORINAGA731ad812011-10-28 09:37:34 +0900435 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
Toshiharu Okadaf646cf92010-11-11 18:27:57 +0900436 depends on PCI
437 select USB_GADGET_DUALSPEED
438 help
439 This is a USB device driver for EG20T PCH.
440 EG20T PCH is the platform controller hub that is used in Intel's
441 general embedded platform. EG20T PCH has USB device interface.
442 Using this interface, it is able to access system devices connected
443 to USB device.
444 This driver enables USB device function.
445 USB device is a USB peripheral controller which
446 supports both full and high speed USB 2.0 data transfers.
447 This driver supports both control transfer and bulk transfer modes.
448 This driver dose not support interrupt transfer or isochronous
449 transfer modes.
450
Tomoya MORINAGA731ad812011-10-28 09:37:34 +0900451 This driver also can be used for LAPIS Semiconductor's ML7213 which is
Tomoya MORINAGA06f1b972011-01-06 09:16:31 +0900452 for IVI(In-Vehicle Infotainment) use.
Tomoya MORINAGA731ad812011-10-28 09:37:34 +0900453 ML7831 is for general purpose use.
454 ML7213/ML7831 is companion chip for Intel Atom E6xx series.
455 ML7213/ML7831 is completely compatible for Intel EG20T PCH.
Tomoya MORINAGA06f1b972011-01-06 09:16:31 +0900456
David Brownella7a19fa2008-08-14 17:04:48 -0700457#
458# LAST -- dummy/emulated controller
459#
Linus Torvalds1da177e2005-04-16 15:20:36 -0700460
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300461config USB_DUMMY_HCD
462 tristate "Dummy HCD (DEVELOPMENT)"
Robert P. J. Dayafd0e0f2008-03-10 15:09:51 -0400463 depends on USB=y || (USB=m && USB_GADGET=m)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700464 select USB_GADGET_DUALSPEED
Tatyana Brokhman1cd8fd22011-06-29 16:41:52 +0300465 select USB_GADGET_SUPERSPEED
Linus Torvalds1da177e2005-04-16 15:20:36 -0700466 help
467 This host controller driver emulates USB, looping all data transfer
468 requests back to a USB "gadget driver" in the same host. The host
469 side is the master; the gadget side is the slave. Gadget drivers
470 can be high, full, or low speed; and they have access to endpoints
471 like those from NET2280, PXA2xx, or SA1100 hardware.
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300472
Linus Torvalds1da177e2005-04-16 15:20:36 -0700473 This may help in some stages of creating a driver to embed in a
474 Linux device, since it lets you debug several parts of the gadget
475 driver without its hardware or drivers being involved.
Felipe Balbi193ab2a2011-06-22 17:28:10 +0300476
Linus Torvalds1da177e2005-04-16 15:20:36 -0700477 Since such a gadget side driver needs to interoperate with a host
478 side Linux-USB device driver, this may help to debug both sides
479 of a USB protocol stack.
480
481 Say "y" to link the driver statically, or "m" to build a
482 dynamically linked module called "dummy_hcd" and force all
483 gadget drivers to also be dynamically linked.
484
Linus Torvalds1da177e2005-04-16 15:20:36 -0700485# NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
486# first and will be selected by default.
487
Alexander Shishkined6c6f42012-05-08 23:29:00 +0300488endmenu
Linus Torvalds1da177e2005-04-16 15:20:36 -0700489
Alan Stern97b2f902011-06-07 11:31:05 -0400490# Selected by UDC drivers that support high-speed operation.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700491config USB_GADGET_DUALSPEED
492 bool
Linus Torvalds1da177e2005-04-16 15:20:36 -0700493
Tatyana Brokhmanbdb64d72011-06-29 16:41:50 +0300494# Selected by UDC drivers that support super-speed opperation
495config USB_GADGET_SUPERSPEED
496 bool
Tatyana Brokhmanbdb64d72011-06-29 16:41:50 +0300497 depends on USB_GADGET_DUALSPEED
498
Linus Torvalds1da177e2005-04-16 15:20:36 -0700499#
500# USB Gadget Drivers
501#
502choice
503 tristate "USB Gadget Drivers"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700504 default USB_ETH
505 help
506 A Linux "Gadget Driver" talks to the USB Peripheral Controller
507 driver through the abstract "gadget" API. Some other operating
508 systems call these "client" drivers, of which "class drivers"
509 are a subset (implementing a USB device class specification).
510 A gadget driver implements one or more USB functions using
511 the peripheral hardware.
512
513 Gadget drivers are hardware-neutral, or "platform independent",
514 except that they sometimes must understand quirks or limitations
515 of the particular controllers they work with. For example, when
516 a controller doesn't support alternate configurations or provide
517 enough of the right types of endpoints, the gadget driver might
518 not be able work with that controller, or might need to implement
519 a less common variant of a device class protocol.
520
521# this first set of drivers all depend on bulk-capable hardware.
522
523config USB_ZERO
524 tristate "Gadget Zero (DEVELOPMENT)"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700525 help
526 Gadget Zero is a two-configuration device. It either sinks and
527 sources bulk data; or it loops back a configurable number of
528 transfers. It also implements control requests, for "chapter 9"
529 conformance. The driver needs only two bulk-capable endpoints, so
530 it can work on top of most device-side usb controllers. It's
531 useful for testing, and is also a working example showing how
532 USB "gadget drivers" can be written.
533
534 Make this be the first driver you try using on top of any new
535 USB peripheral controller driver. Then you can use host-side
536 test software, like the "usbtest" driver, to put your hardware
537 and its driver through a basic set of functional tests.
538
539 Gadget Zero also works with the host-side "usb-skeleton" driver,
540 and with many kinds of host-side test software. You may need
541 to tweak product and vendor IDs before host software knows about
542 this device, and arrange to select an appropriate configuration.
543
544 Say "y" to link the driver statically, or "m" to build a
545 dynamically linked module called "g_zero".
546
547config USB_ZERO_HNPTEST
548 boolean "HNP Test Device"
549 depends on USB_ZERO && USB_OTG
550 help
551 You can configure this device to enumerate using the device
552 identifiers of the USB-OTG test device. That means that when
553 this gadget connects to another OTG device, with this one using
554 the "B-Peripheral" role, that device will use HNP to let this
555 one serve as the USB host instead (in the "B-Host" role).
556
Bryan Wuc6994e62009-06-03 09:17:58 -0400557config USB_AUDIO
558 tristate "Audio Gadget (EXPERIMENTAL)"
559 depends on SND
Randy Dunlap04950732009-07-03 13:26:57 -0700560 select SND_PCM
Bryan Wuc6994e62009-06-03 09:17:58 -0400561 help
Jassi Brar132fcb42012-02-02 22:01:34 +0530562 This Gadget Audio driver is compatible with USB Audio Class
563 specification 2.0. It implements 1 AudioControl interface,
564 1 AudioStreaming Interface each for USB-OUT and USB-IN.
565 Number of channels, sample rate and sample size can be
566 specified as module parameters.
567 This driver doesn't expect any real Audio codec to be present
568 on the device - the audio streams are simply sinked to and
569 sourced from a virtual ALSA sound card created. The user-space
570 application may choose to do whatever it wants with the data
571 received from the USB Host and choose to provide whatever it
572 wants as audio data to the USB Host.
Bryan Wuc6994e62009-06-03 09:17:58 -0400573
574 Say "y" to link the driver statically, or "m" to build a
575 dynamically linked module called "g_audio".
576
Jassi Brar132fcb42012-02-02 22:01:34 +0530577config GADGET_UAC1
578 bool "UAC 1.0 (Legacy)"
579 depends on USB_AUDIO
580 help
581 If you instead want older UAC Spec-1.0 driver that also has audio
582 paths hardwired to the Audio codec chip on-board and doesn't work
583 without one.
584
Linus Torvalds1da177e2005-04-16 15:20:36 -0700585config USB_ETH
586 tristate "Ethernet Gadget (with CDC Ethernet support)"
587 depends on NET
Randy Dunlap9e221be2009-09-07 17:08:39 -0700588 select CRC32
Linus Torvalds1da177e2005-04-16 15:20:36 -0700589 help
Brian Niebuhr9b39e9d2009-08-14 10:04:22 -0500590 This driver implements Ethernet style communication, in one of
591 several ways:
Linus Torvalds1da177e2005-04-16 15:20:36 -0700592
593 - The "Communication Device Class" (CDC) Ethernet Control Model.
594 That protocol is often avoided with pure Ethernet adapters, in
595 favor of simpler vendor-specific hardware, but is widely
596 supported by firmware for smart network devices.
597
598 - On hardware can't implement that protocol, a simple CDC subset
599 is used, placing fewer demands on USB.
600
Brian Niebuhr9b39e9d2009-08-14 10:04:22 -0500601 - CDC Ethernet Emulation Model (EEM) is a newer standard that has
602 a simpler interface that can be used by more USB hardware.
603
604 RNDIS support is an additional option, more demanding than than
605 subset.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700606
607 Within the USB device, this gadget driver exposes a network device
608 "usbX", where X depends on what other networking devices you have.
609 Treat it like a two-node Ethernet link: host, and gadget.
610
611 The Linux-USB host-side "usbnet" driver interoperates with this
612 driver, so that deep I/O queues can be supported. On 2.4 kernels,
613 use "CDCEther" instead, if you're using the CDC option. That CDC
614 mode should also interoperate with standard CDC Ethernet class
615 drivers on other host operating systems.
616
617 Say "y" to link the driver statically, or "m" to build a
618 dynamically linked module called "g_ether".
619
620config USB_ETH_RNDIS
Robert P. J. Dayafd0e0f2008-03-10 15:09:51 -0400621 bool "RNDIS support"
622 depends on USB_ETH
Linus Torvalds1da177e2005-04-16 15:20:36 -0700623 default y
624 help
625 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
626 and Microsoft provides redistributable binary RNDIS drivers for
627 older versions of Windows.
628
629 If you say "y" here, the Ethernet gadget driver will try to provide
630 a second device configuration, supporting RNDIS to talk to such
631 Microsoft USB hosts.
632
633 To make MS-Windows work with this, use Documentation/usb/linux.inf
634 as the "driver info file". For versions of MS-Windows older than
635 XP, you'll need to download drivers from Microsoft's website; a URL
636 is given in comments found in that info file.
637
Brian Niebuhr9b39e9d2009-08-14 10:04:22 -0500638config USB_ETH_EEM
639 bool "Ethernet Emulation Model (EEM) support"
640 depends on USB_ETH
641 default n
642 help
643 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
644 and therefore can be supported by more hardware. Technically ECM and
645 EEM are designed for different applications. The ECM model extends
646 the network interface to the target (e.g. a USB cable modem), and the
647 EEM model is for mobile devices to communicate with hosts using
648 ethernet over USB. For Linux gadgets, however, the interface with
649 the host is the same (a usbX device), so the differences are minimal.
650
651 If you say "y" here, the Ethernet gadget driver will use the EEM
652 protocol rather than ECM. If unsure, say "n".
653
Yauheni Kaliuta6c34d282010-12-08 13:12:06 +0200654config USB_G_NCM
655 tristate "Network Control Model (NCM) support"
656 depends on NET
657 select CRC32
658 help
659 This driver implements USB CDC NCM subclass standard. NCM is
660 an advanced protocol for Ethernet encapsulation, allows grouping
Fabio Baltierib55dd322012-03-10 22:44:19 +0100661 of several ethernet frames into one USB transfer and different
Yauheni Kaliuta6c34d282010-12-08 13:12:06 +0200662 alignment possibilities.
663
664 Say "y" to link the driver statically, or "m" to build a
665 dynamically linked module called "g_ncm".
666
Linus Torvalds1da177e2005-04-16 15:20:36 -0700667config USB_GADGETFS
668 tristate "Gadget Filesystem (EXPERIMENTAL)"
669 depends on EXPERIMENTAL
670 help
671 This driver provides a filesystem based API that lets user mode
672 programs implement a single-configuration USB device, including
673 endpoint I/O and control requests that don't relate to enumeration.
674 All endpoints, transfer speeds, and transfer types supported by
675 the hardware are available, through read() and write() calls.
676
Robert P. J. Dayafd0e0f2008-03-10 15:09:51 -0400677 Currently, this option is still labelled as EXPERIMENTAL because
678 of existing race conditions in the underlying in-kernel AIO core.
679
Linus Torvalds1da177e2005-04-16 15:20:36 -0700680 Say "y" to link the driver statically, or "m" to build a
681 dynamically linked module called "gadgetfs".
682
Michal Nazarewiczc6c56002010-05-05 12:53:15 +0200683config USB_FUNCTIONFS
684 tristate "Function Filesystem (EXPERIMENTAL)"
685 depends on EXPERIMENTAL
Michal Nazarewiczf8dae532010-06-25 16:29:27 +0200686 select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
Michal Nazarewiczc6c56002010-05-05 12:53:15 +0200687 help
Michael Prokopeabf0f52010-09-06 09:53:48 +0200688 The Function Filesystem (FunctionFS) lets one create USB
689 composite functions in user space in the same way GadgetFS
Michal Nazarewiczc6c56002010-05-05 12:53:15 +0200690 lets one create USB gadgets in user space. This allows creation
691 of composite gadgets such that some of the functions are
692 implemented in kernel space (for instance Ethernet, serial or
693 mass storage) and other are implemented in user space.
694
Michal Nazarewiczf8dae532010-06-25 16:29:27 +0200695 If you say "y" or "m" here you will be able what kind of
696 configurations the gadget will provide.
697
Michal Nazarewiczc6c56002010-05-05 12:53:15 +0200698 Say "y" to link the driver statically, or "m" to build
699 a dynamically linked module called "g_ffs".
700
701config USB_FUNCTIONFS_ETH
Michal Nazarewiczf8dae532010-06-25 16:29:27 +0200702 bool "Include configuration with CDC ECM (Ethernet)"
Randy Dunlap17b27652010-05-13 09:41:12 -0700703 depends on USB_FUNCTIONFS && NET
Michal Nazarewiczc6c56002010-05-05 12:53:15 +0200704 help
Michael Prokopeabf0f52010-09-06 09:53:48 +0200705 Include a configuration with CDC ECM function (Ethernet) and the
706 Function Filesystem.
Michal Nazarewiczc6c56002010-05-05 12:53:15 +0200707
708config USB_FUNCTIONFS_RNDIS
Michal Nazarewiczf8dae532010-06-25 16:29:27 +0200709 bool "Include configuration with RNDIS (Ethernet)"
Randy Dunlap17b27652010-05-13 09:41:12 -0700710 depends on USB_FUNCTIONFS && NET
Michal Nazarewiczc6c56002010-05-05 12:53:15 +0200711 help
Michael Prokopeabf0f52010-09-06 09:53:48 +0200712 Include a configuration with RNDIS function (Ethernet) and the Filesystem.
Michal Nazarewiczc6c56002010-05-05 12:53:15 +0200713
714config USB_FUNCTIONFS_GENERIC
715 bool "Include 'pure' configuration"
Michal Nazarewiczf8dae532010-06-25 16:29:27 +0200716 depends on USB_FUNCTIONFS
Michal Nazarewiczc6c56002010-05-05 12:53:15 +0200717 help
Michal Nazarewiczf8dae532010-06-25 16:29:27 +0200718 Include a configuration with the Function Filesystem alone with
719 no Ethernet interface.
Michal Nazarewiczc6c56002010-05-05 12:53:15 +0200720
Linus Torvalds1da177e2005-04-16 15:20:36 -0700721config USB_FILE_STORAGE
Alan Stern664a51a2011-06-15 16:31:37 -0400722 tristate "File-backed Storage Gadget (DEPRECATED)"
Randy Dunlap87840282007-03-21 13:57:51 -0700723 depends on BLOCK
Linus Torvalds1da177e2005-04-16 15:20:36 -0700724 help
725 The File-backed Storage Gadget acts as a USB Mass Storage
726 disk drive. As its storage repository it can use a regular
727 file or a block device (in much the same way as the "loop"
728 device driver), specified as a module parameter.
729
730 Say "y" to link the driver statically, or "m" to build a
731 dynamically linked module called "g_file_storage".
732
Alan Stern664a51a2011-06-15 16:31:37 -0400733 NOTE: This driver is deprecated. Its replacement is the
734 Mass Storage Gadget.
735
Linus Torvalds1da177e2005-04-16 15:20:36 -0700736config USB_FILE_STORAGE_TEST
737 bool "File-backed Storage Gadget testing version"
738 depends on USB_FILE_STORAGE
739 default n
740 help
741 Say "y" to generate the larger testing version of the
742 File-backed Storage Gadget, useful for probing the
743 behavior of USB Mass Storage hosts. Not needed for
744 normal operation.
745
Michal Nazarewiczd23b0f02009-11-09 14:15:20 +0100746config USB_MASS_STORAGE
747 tristate "Mass Storage Gadget"
748 depends on BLOCK
749 help
750 The Mass Storage Gadget acts as a USB Mass Storage disk drive.
751 As its storage repository it can use a regular file or a block
752 device (in much the same way as the "loop" device driver),
753 specified as a module parameter or sysfs option.
754
Alan Stern664a51a2011-06-15 16:31:37 -0400755 This driver is an updated replacement for the deprecated
756 File-backed Storage Gadget (g_file_storage).
Michal Nazarewiczd23b0f02009-11-09 14:15:20 +0100757
758 Say "y" to link the driver statically, or "m" to build
Alan Stern664a51a2011-06-15 16:31:37 -0400759 a dynamically linked module called "g_mass_storage".
Michal Nazarewiczd23b0f02009-11-09 14:15:20 +0100760
Sebastian Andrzej Siewiorc52661d2012-05-03 19:51:36 -0700761config USB_GADGET_TARGET
762 tristate "USB Gadget Target Fabric Module"
763 depends on TARGET_CORE
764 help
765 This fabric is an USB gadget. Two USB protocols are supported that is
766 BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
767 advertised on alternative interface 0 (primary) and UAS is on
768 alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
769 UAS utilizes the USB 3.0 feature called streams support.
770
Linus Torvalds1da177e2005-04-16 15:20:36 -0700771config USB_G_SERIAL
Felipe Balbi30867752008-08-18 17:39:30 -0700772 tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700773 help
774 The Serial Gadget talks to the Linux-USB generic serial driver.
775 This driver supports a CDC-ACM module option, which can be used
776 to interoperate with MS-Windows hosts or with the Linux-USB
777 "cdc-acm" driver.
778
Felipe Balbi30867752008-08-18 17:39:30 -0700779 This driver also supports a CDC-OBEX option. You will need a
780 user space OBEX server talking to /dev/ttyGS*, since the kernel
781 itself doesn't implement the OBEX protocol.
782
Linus Torvalds1da177e2005-04-16 15:20:36 -0700783 Say "y" to link the driver statically, or "m" to build a
784 dynamically linked module called "g_serial".
785
786 For more information, see Documentation/usb/gadget_serial.txt
787 which includes instructions and a "driver info file" needed to
Felipe Balbi30867752008-08-18 17:39:30 -0700788 make MS-Windows work with CDC ACM.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700789
Ben Williamsonf2ebf92c2006-08-01 11:28:16 +1000790config USB_MIDI_GADGET
791 tristate "MIDI Gadget (EXPERIMENTAL)"
792 depends on SND && EXPERIMENTAL
793 select SND_RAWMIDI
794 help
795 The MIDI Gadget acts as a USB Audio device, with one MIDI
796 input and one MIDI output. These MIDI jacks appear as
797 a sound "card" in the ALSA sound system. Other MIDI
798 connections can then be made on the gadget system, using
799 ALSA's aconnect utility etc.
800
801 Say "y" to link the driver statically, or "m" to build a
802 dynamically linked module called "g_midi".
803
Craig W. Nadler25a010c2007-11-11 15:00:15 -0800804config USB_G_PRINTER
805 tristate "Printer Gadget"
806 help
807 The Printer Gadget channels data between the USB host and a
808 userspace program driving the print engine. The user space
809 program reads and writes the device file /dev/g_printer to
810 receive or send printer data. It can use ioctl calls to
811 the device file to get or set printer status.
812
813 Say "y" to link the driver statically, or "m" to build a
814 dynamically linked module called "g_printer".
815
816 For more information, see Documentation/usb/gadget_printer.txt
817 which includes sample code for accessing the device file.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700818
David Brownell19e20682008-06-19 18:20:26 -0700819config USB_CDC_COMPOSITE
820 tristate "CDC Composite Device (Ethernet and ACM)"
Randy Dunlap4ddd9ec2008-07-03 14:44:59 -0700821 depends on NET
David Brownell19e20682008-06-19 18:20:26 -0700822 help
823 This driver provides two functions in one configuration:
824 a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
825
826 This driver requires four bulk and two interrupt endpoints,
827 plus the ability to handle altsettings. Not all peripheral
828 controllers are that capable.
829
830 Say "y" to link the driver statically, or "m" to build a
831 dynamically linked module.
832
Felipe Balbif358f5b2010-01-05 16:10:13 +0200833config USB_G_NOKIA
834 tristate "Nokia composite gadget"
835 depends on PHONET
836 help
837 The Nokia composite gadget provides support for acm, obex
838 and phonet in only one composite gadget driver.
839
840 It's only really useful for N900 hardware. If you're building
841 a kernel for N900, say Y or M here. If unsure, say N.
842
Klaus Schwarzkopffa3ae0c2011-10-10 10:32:23 +0200843config USB_G_ACM_MS
844 tristate "CDC Composite Device (ACM and mass storage)"
845 depends on BLOCK
846 help
847 This driver provides two functions in one configuration:
848 a mass storage, and a CDC ACM (serial port) link.
849
850 Say "y" to link the driver statically, or "m" to build a
851 dynamically linked module called "g_acm_ms".
852
Michal Nazarewiczf176a5d2009-11-09 14:15:27 +0100853config USB_G_MULTI
854 tristate "Multifunction Composite Gadget (EXPERIMENTAL)"
Randy Dunlap5791e102009-12-06 10:03:02 -0800855 depends on BLOCK && NET
Michal Nazarewicz279cc492010-06-21 13:57:03 +0200856 select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
Michal Nazarewiczf176a5d2009-11-09 14:15:27 +0100857 help
858 The Multifunction Composite Gadget provides Ethernet (RNDIS
859 and/or CDC Ethernet), mass storage and ACM serial link
860 interfaces.
861
Randy Dunlap5791e102009-12-06 10:03:02 -0800862 You will be asked to choose which of the two configurations is
Michal Nazarewiczf176a5d2009-11-09 14:15:27 +0100863 to be available in the gadget. At least one configuration must
Randy Dunlap5791e102009-12-06 10:03:02 -0800864 be chosen to make the gadget usable. Selecting more than one
Michal Nazarewiczf176a5d2009-11-09 14:15:27 +0100865 configuration will prevent Windows from automatically detecting
Randy Dunlap5791e102009-12-06 10:03:02 -0800866 the gadget as a composite gadget, so an INF file will be needed to
Michal Nazarewiczf176a5d2009-11-09 14:15:27 +0100867 use the gadget.
868
869 Say "y" to link the driver statically, or "m" to build a
870 dynamically linked module called "g_multi".
871
872config USB_G_MULTI_RNDIS
873 bool "RNDIS + CDC Serial + Storage configuration"
874 depends on USB_G_MULTI
875 default y
876 help
877 This option enables a configuration with RNDIS, CDC Serial and
878 Mass Storage functions available in the Multifunction Composite
Randy Dunlap5791e102009-12-06 10:03:02 -0800879 Gadget. This is the configuration dedicated for Windows since RNDIS
880 is Microsoft's protocol.
Michal Nazarewiczf176a5d2009-11-09 14:15:27 +0100881
882 If unsure, say "y".
883
884config USB_G_MULTI_CDC
885 bool "CDC Ethernet + CDC Serial + Storage configuration"
886 depends on USB_G_MULTI
887 default n
888 help
889 This option enables a configuration with CDC Ethernet (ECM), CDC
890 Serial and Mass Storage functions available in the Multifunction
Randy Dunlap5791e102009-12-06 10:03:02 -0800891 Composite Gadget.
Michal Nazarewiczf176a5d2009-11-09 14:15:27 +0100892
893 If unsure, say "y".
894
Fabien Chouteau71adf112010-04-08 09:31:15 +0200895config USB_G_HID
896 tristate "HID Gadget"
897 help
898 The HID gadget driver provides generic emulation of USB
899 Human Interface Devices (HID).
900
901 For more information, see Documentation/usb/gadget_hid.txt which
902 includes sample code for accessing the device files.
903
904 Say "y" to link the driver statically, or "m" to build a
905 dynamically linked module called "g_hid".
Michal Nazarewiczf176a5d2009-11-09 14:15:27 +0100906
stephane duvergerf6c826a2010-07-12 18:37:53 +0200907config USB_G_DBGP
908 tristate "EHCI Debug Device Gadget"
909 help
910 This gadget emulates an EHCI Debug device. This is useful when you want
911 to interact with an EHCI Debug Port.
912
913 Say "y" to link the driver statically, or "m" to build a
914 dynamically linked module called "g_dbgp".
915
916if USB_G_DBGP
917choice
918 prompt "EHCI Debug Device mode"
919 default USB_G_DBGP_SERIAL
920
921config USB_G_DBGP_PRINTK
922 depends on USB_G_DBGP
923 bool "printk"
924 help
925 Directly printk() received data. No interaction.
926
927config USB_G_DBGP_SERIAL
928 depends on USB_G_DBGP
929 bool "serial"
930 help
931 Userland can interact using /dev/ttyGSxxx.
932endchoice
933endif
934
Linus Torvalds1da177e2005-04-16 15:20:36 -0700935# put drivers that need isochronous transfer support (for audio
936# or video class gadget drivers), or specific hardware, here.
Laurent Pincharta99141272010-05-02 20:57:42 +0200937config USB_G_WEBCAM
938 tristate "USB Webcam Gadget"
Randy Dunlap24337c12010-05-05 15:46:26 -0700939 depends on VIDEO_DEV
Laurent Pincharta99141272010-05-02 20:57:42 +0200940 help
941 The Webcam Gadget acts as a composite USB Audio and Video Class
942 device. It provides a userspace API to process UVC control requests
943 and stream video data to the host.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700944
Laurent Pincharta99141272010-05-02 20:57:42 +0200945 Say "y" to link the driver statically, or "m" to build a
946 dynamically linked module called "g_webcam".
Linus Torvalds1da177e2005-04-16 15:20:36 -0700947
948endchoice
949
Denis Chengb75be4a2008-01-24 16:36:31 +0800950endif # USB_GADGET