Loading...
1# SPDX-License-Identifier: GPL-2.0
2#
3# USB Gadget support on a system involves
4# (a) a peripheral controller, and
5# (b) the gadget driver using it.
6#
7# NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
8#
9# - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10# - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11# - Some systems have both kinds of controllers.
12#
13# With help from a special transceiver and a "Mini-AB" jack, systems with
14# both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
15#
16
17menuconfig USB_GADGET
18 tristate "USB Gadget Support"
19 select USB_COMMON
20 select NLS
21 help
22 USB is a host/device protocol, organized with one host (such as a
23 PC) controlling up to 127 peripheral devices.
24 The USB hardware is asymmetric, which makes it easier to set up:
25 you can't connect a "to-the-host" connector to a peripheral.
26
27 Linux can run in the host, or in the peripheral. In both cases
28 you need a low level bus controller driver, and some software
29 talking to it. Peripheral controllers are often discrete silicon,
30 or are integrated with the CPU in a microcontroller. The more
31 familiar host side controllers have names like "EHCI", "OHCI",
32 or "UHCI", and are usually integrated into southbridges on PC
33 motherboards.
34
35 Enable this configuration option if you want to run Linux inside
36 a USB peripheral device. Configure one hardware driver for your
37 peripheral/device side bus controller, and a "gadget driver" for
38 your peripheral protocol. (If you use modular gadget drivers,
39 you may configure more than one.)
40
41 If in doubt, say "N" and don't enable these drivers; most people
42 don't have this kind of hardware (except maybe inside Linux PDAs).
43
44 For more information, see <http://www.linux-usb.org/gadget> and
45 the kernel documentation for this API.
46
47if USB_GADGET
48
49config USB_GADGET_DEBUG
50 bool "Debugging messages (DEVELOPMENT)"
51 depends on DEBUG_KERNEL
52 help
53 Many controller and gadget drivers will print some debugging
54 messages if you use this option to ask for those messages.
55
56 Avoid enabling these messages, even if you're actively
57 debugging such a driver. Many drivers will emit so many
58 messages that the driver timings are affected, which will
59 either create new failure modes or remove the one you're
60 trying to track down. Never enable these messages for a
61 production build.
62
63config USB_GADGET_VERBOSE
64 bool "Verbose debugging Messages (DEVELOPMENT)"
65 depends on USB_GADGET_DEBUG
66 help
67 Many controller and gadget drivers will print verbose debugging
68 messages if you use this option to ask for those messages.
69
70 Avoid enabling these messages, even if you're actively
71 debugging such a driver. Many drivers will emit so many
72 messages that the driver timings are affected, which will
73 either create new failure modes or remove the one you're
74 trying to track down. Never enable these messages for a
75 production build.
76
77config USB_GADGET_DEBUG_FILES
78 bool "Debugging information files (DEVELOPMENT)"
79 depends on PROC_FS
80 help
81 Some of the drivers in the "gadget" framework can expose
82 debugging information in files such as /proc/driver/udc
83 (for a peripheral controller). The information in these
84 files may help when you're troubleshooting or bringing up a
85 driver on a new board. Enable these files by choosing "Y"
86 here. If in doubt, or to conserve kernel memory, say "N".
87
88config USB_GADGET_DEBUG_FS
89 bool "Debugging information files in debugfs (DEVELOPMENT)"
90 depends on DEBUG_FS
91 help
92 Some of the drivers in the "gadget" framework can expose
93 debugging information in files under /sys/kernel/debug/.
94 The information in these files may help when you're
95 troubleshooting or bringing up a driver on a new board.
96 Enable these files by choosing "Y" here. If in doubt, or
97 to conserve kernel memory, say "N".
98
99config USB_GADGET_VBUS_DRAW
100 int "Maximum VBUS Power usage (2-500 mA)"
101 range 2 500
102 default 2
103 help
104 Some devices need to draw power from USB when they are
105 configured, perhaps to operate circuitry or to recharge
106 batteries. This is in addition to any local power supply,
107 such as an AC adapter or batteries.
108
109 Enter the maximum power your device draws through USB, in
110 milliAmperes. The permitted range of values is 2 - 500 mA;
111 0 mA would be legal, but can make some hosts misbehave.
112
113 This value will be used except for system-specific gadget
114 drivers that have more specific information.
115
116config USB_GADGET_STORAGE_NUM_BUFFERS
117 int "Number of storage pipeline buffers"
118 range 2 256
119 default 2
120 help
121 Usually 2 buffers are enough to establish a good buffering
122 pipeline. The number may be increased in order to compensate
123 for a bursty VFS behaviour. For instance there may be CPU wake up
124 latencies that makes the VFS to appear bursty in a system with
125 an CPU on-demand governor. Especially if DMA is doing IO to
126 offload the CPU. In this case the CPU will go into power
127 save often and spin up occasionally to move data within VFS.
128 If selecting USB_GADGET_DEBUG_FILES this value may be set by
129 a module parameter as well.
130 If unsure, say 2.
131
132config U_SERIAL_CONSOLE
133 bool "Serial gadget console support"
134 depends on USB_U_SERIAL
135 help
136 It supports the serial gadget can be used as a console.
137
138source "drivers/usb/gadget/udc/Kconfig"
139
140#
141# USB Gadget Drivers
142#
143
144# composite based drivers
145config USB_LIBCOMPOSITE
146 tristate
147 select CONFIGFS_FS
148 depends on USB_GADGET
149
150config USB_F_ACM
151 tristate
152
153config USB_F_SS_LB
154 tristate
155
156config USB_U_SERIAL
157 tristate
158
159config USB_U_ETHER
160 tristate
161
162config USB_U_AUDIO
163 tristate
164
165config USB_F_SERIAL
166 tristate
167
168config USB_F_OBEX
169 tristate
170
171config USB_F_NCM
172 tristate
173
174config USB_F_ECM
175 tristate
176
177config USB_F_PHONET
178 tristate
179
180config USB_F_EEM
181 tristate
182
183config USB_F_SUBSET
184 tristate
185
186config USB_F_RNDIS
187 tristate
188
189config USB_F_MASS_STORAGE
190 tristate
191
192config USB_F_FS
193 tristate
194
195config USB_F_UAC1
196 tristate
197
198config USB_F_UAC1_LEGACY
199 tristate
200
201config USB_F_UAC2
202 tristate
203
204config USB_F_UVC
205 tristate
206 select UVC_COMMON
207
208config USB_F_MIDI
209 tristate
210
211config USB_F_MIDI2
212 tristate
213
214config USB_F_HID
215 tristate
216
217config USB_F_PRINTER
218 tristate
219
220config USB_F_TCM
221 tristate
222
223# this first set of drivers all depend on bulk-capable hardware.
224
225config USB_CONFIGFS
226 tristate "USB Gadget functions configurable through configfs"
227 select USB_LIBCOMPOSITE
228 help
229 A Linux USB "gadget" can be set up through configfs.
230 If this is the case, the USB functions (which from the host's
231 perspective are seen as interfaces) and configurations are
232 specified simply by creating appropriate directories in configfs.
233 Associating functions with configurations is done by creating
234 appropriate symbolic links.
235 For more information see Documentation/usb/gadget_configfs.rst.
236
237config USB_CONFIGFS_SERIAL
238 bool "Generic serial bulk in/out"
239 depends on USB_CONFIGFS
240 depends on TTY
241 select USB_U_SERIAL
242 select USB_F_SERIAL
243 help
244 The function talks to the Linux-USB generic serial driver.
245
246config USB_CONFIGFS_ACM
247 bool "Abstract Control Model (CDC ACM)"
248 depends on USB_CONFIGFS
249 depends on TTY
250 select USB_U_SERIAL
251 select USB_F_ACM
252 help
253 ACM serial link. This function can be used to interoperate with
254 MS-Windows hosts or with the Linux-USB "cdc-acm" driver.
255
256config USB_CONFIGFS_OBEX
257 bool "Object Exchange Model (CDC OBEX)"
258 depends on USB_CONFIGFS
259 depends on TTY
260 select USB_U_SERIAL
261 select USB_F_OBEX
262 help
263 You will need a user space OBEX server talking to /dev/ttyGS*,
264 since the kernel itself doesn't implement the OBEX protocol.
265
266config USB_CONFIGFS_NCM
267 bool "Network Control Model (CDC NCM)"
268 depends on USB_CONFIGFS
269 depends on NET
270 select USB_U_ETHER
271 select USB_F_NCM
272 select CRC32
273 help
274 NCM is an advanced protocol for Ethernet encapsulation, allows
275 grouping of several ethernet frames into one USB transfer and
276 different alignment possibilities.
277
278config USB_CONFIGFS_ECM
279 bool "Ethernet Control Model (CDC ECM)"
280 depends on USB_CONFIGFS
281 depends on NET
282 select USB_U_ETHER
283 select USB_F_ECM
284 help
285 The "Communication Device Class" (CDC) Ethernet Control Model.
286 That protocol is often avoided with pure Ethernet adapters, in
287 favor of simpler vendor-specific hardware, but is widely
288 supported by firmware for smart network devices.
289
290config USB_CONFIGFS_ECM_SUBSET
291 bool "Ethernet Control Model (CDC ECM) subset"
292 depends on USB_CONFIGFS
293 depends on NET
294 select USB_U_ETHER
295 select USB_F_SUBSET
296 help
297 On hardware that can't implement the full protocol,
298 a simple CDC subset is used, placing fewer demands on USB.
299
300config USB_CONFIGFS_RNDIS
301 bool "RNDIS"
302 depends on USB_CONFIGFS
303 depends on NET
304 select USB_U_ETHER
305 select USB_F_RNDIS
306 help
307 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
308 and Microsoft provides redistributable binary RNDIS drivers for
309 older versions of Windows.
310
311 To make MS-Windows work with this, use Documentation/usb/linux.inf
312 as the "driver info file". For versions of MS-Windows older than
313 XP, you'll need to download drivers from Microsoft's website; a URL
314 is given in comments found in that info file.
315
316config USB_CONFIGFS_EEM
317 bool "Ethernet Emulation Model (EEM)"
318 depends on USB_CONFIGFS
319 depends on NET
320 select USB_U_ETHER
321 select USB_F_EEM
322 select CRC32
323 help
324 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
325 and therefore can be supported by more hardware. Technically ECM and
326 EEM are designed for different applications. The ECM model extends
327 the network interface to the target (e.g. a USB cable modem), and the
328 EEM model is for mobile devices to communicate with hosts using
329 ethernet over USB. For Linux gadgets, however, the interface with
330 the host is the same (a usbX device), so the differences are minimal.
331
332config USB_CONFIGFS_PHONET
333 bool "Phonet protocol"
334 depends on USB_CONFIGFS
335 depends on NET
336 depends on PHONET
337 select USB_U_ETHER
338 select USB_F_PHONET
339 help
340 The Phonet protocol implementation for USB device.
341
342config USB_CONFIGFS_MASS_STORAGE
343 bool "Mass storage"
344 depends on USB_CONFIGFS
345 depends on BLOCK
346 select USB_F_MASS_STORAGE
347 help
348 The Mass Storage Gadget acts as a USB Mass Storage disk drive.
349 As its storage repository it can use a regular file or a block
350 device (in much the same way as the "loop" device driver),
351 specified as a module parameter or sysfs option.
352
353config USB_CONFIGFS_F_LB_SS
354 bool "Loopback and sourcesink function (for testing)"
355 depends on USB_CONFIGFS
356 select USB_F_SS_LB
357 help
358 Loopback function loops back a configurable number of transfers.
359 Sourcesink function either sinks and sources bulk data.
360 It also implements control requests, for "chapter 9" conformance.
361 Make this be the first driver you try using on top of any new
362 USB peripheral controller driver. Then you can use host-side
363 test software, like the "usbtest" driver, to put your hardware
364 and its driver through a basic set of functional tests.
365
366config USB_CONFIGFS_F_FS
367 bool "Function filesystem (FunctionFS)"
368 depends on USB_CONFIGFS
369 select USB_F_FS
370 help
371 The Function Filesystem (FunctionFS) lets one create USB
372 composite functions in user space in the same way GadgetFS
373 lets one create USB gadgets in user space. This allows creation
374 of composite gadgets such that some of the functions are
375 implemented in kernel space (for instance Ethernet, serial or
376 mass storage) and other are implemented in user space.
377
378config USB_CONFIGFS_F_UAC1
379 bool "Audio Class 1.0"
380 depends on USB_CONFIGFS
381 depends on SND
382 select USB_LIBCOMPOSITE
383 select SND_PCM
384 select USB_U_AUDIO
385 select USB_F_UAC1
386 help
387 This Audio function implements 1 AudioControl interface,
388 1 AudioStreaming Interface each for USB-OUT and USB-IN.
389 This driver doesn't expect any real Audio codec to be present
390 on the device - the audio streams are simply sinked to and
391 sourced from a virtual ALSA sound card created. The user-space
392 application may choose to do whatever it wants with the data
393 received from the USB Host and choose to provide whatever it
394 wants as audio data to the USB Host.
395
396config USB_CONFIGFS_F_UAC1_LEGACY
397 bool "Audio Class 1.0 (legacy implementation)"
398 depends on USB_CONFIGFS
399 depends on SND
400 select USB_LIBCOMPOSITE
401 select SND_PCM
402 select USB_F_UAC1_LEGACY
403 help
404 This Audio function implements 1 AudioControl interface,
405 1 AudioStreaming Interface each for USB-OUT and USB-IN.
406 This is a legacy driver and requires a real Audio codec
407 to be present on the device.
408
409config USB_CONFIGFS_F_UAC2
410 bool "Audio Class 2.0"
411 depends on USB_CONFIGFS
412 depends on SND
413 select USB_LIBCOMPOSITE
414 select SND_PCM
415 select USB_U_AUDIO
416 select USB_F_UAC2
417 help
418 This Audio function is compatible with USB Audio Class
419 specification 2.0. It implements 1 AudioControl interface,
420 1 AudioStreaming Interface each for USB-OUT and USB-IN.
421 This driver doesn't expect any real Audio codec to be present
422 on the device - the audio streams are simply sinked to and
423 sourced from a virtual ALSA sound card created. The user-space
424 application may choose to do whatever it wants with the data
425 received from the USB Host and choose to provide whatever it
426 wants as audio data to the USB Host.
427
428config USB_CONFIGFS_F_MIDI
429 bool "MIDI function"
430 depends on USB_CONFIGFS
431 depends on SND
432 select USB_LIBCOMPOSITE
433 select SND_RAWMIDI
434 select USB_F_MIDI
435 help
436 The MIDI Function acts as a USB Audio device, with one MIDI
437 input and one MIDI output. These MIDI jacks appear as
438 a sound "card" in the ALSA sound system. Other MIDI
439 connections can then be made on the gadget system, using
440 ALSA's aconnect utility etc.
441
442config USB_CONFIGFS_F_MIDI2
443 bool "MIDI 2.0 function"
444 depends on USB_CONFIGFS
445 depends on SND
446 select USB_LIBCOMPOSITE
447 select SND_UMP
448 select SND_UMP_LEGACY_RAWMIDI
449 select USB_F_MIDI2
450 help
451 The MIDI 2.0 function driver provides the generic emulated
452 USB MIDI 2.0 interface, looped back to ALSA UMP rawmidi
453 device on the gadget host. It supports UMP 1.1 spec and
454 responds UMP Stream messages for UMP Endpoint and Function
455 Block information / configuration.
456
457config USB_CONFIGFS_F_HID
458 bool "HID function"
459 depends on USB_CONFIGFS
460 select USB_F_HID
461 help
462 The HID function driver provides generic emulation of USB
463 Human Interface Devices (HID).
464
465 For more information, see Documentation/usb/gadget_hid.rst.
466
467config USB_CONFIGFS_F_UVC
468 bool "USB Webcam function"
469 depends on USB_CONFIGFS
470 depends on VIDEO_DEV
471 depends on VIDEO_DEV
472 select VIDEOBUF2_DMA_SG
473 select VIDEOBUF2_VMALLOC
474 select USB_F_UVC
475 help
476 The Webcam function acts as a composite USB Audio and Video Class
477 device. It provides a userspace API to process UVC control requests
478 and stream video data to the host.
479
480config USB_CONFIGFS_F_PRINTER
481 bool "Printer function"
482 select USB_F_PRINTER
483 depends on USB_CONFIGFS
484 help
485 The Printer function channels data between the USB host and a
486 userspace program driving the print engine. The user space
487 program reads and writes the device file /dev/g_printer<X> to
488 receive or send printer data. It can use ioctl calls to
489 the device file to get or set printer status.
490
491 For more information, see Documentation/usb/gadget_printer.rst
492 which includes sample code for accessing the device file.
493
494config USB_CONFIGFS_F_TCM
495 bool "USB Gadget Target Fabric"
496 depends on TARGET_CORE
497 depends on USB_CONFIGFS
498 select USB_LIBCOMPOSITE
499 select USB_F_TCM
500 help
501 This fabric is a USB gadget component. Two USB protocols are
502 supported that is BBB or BOT (Bulk Only Transport) and UAS
503 (USB Attached SCSI). BOT is advertised on alternative
504 interface 0 (primary) and UAS is on alternative interface 1.
505 Both protocols can work on USB2.0 and USB3.0.
506 UAS utilizes the USB 3.0 feature called streams support.
507
508source "drivers/usb/gadget/legacy/Kconfig"
509
510endif # USB_GADGET
1#
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).
10# - Some systems have both kinds of controllers.
11#
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#
15
16menuconfig USB_GADGET
17 tristate "USB Gadget Support"
18 select NLS
19 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
29 familiar host side controllers have names like "EHCI", "OHCI",
30 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
45if USB_GADGET
46
47config USB_GADGET_DEBUG
48 boolean "Debugging messages (DEVELOPMENT)"
49 depends on DEBUG_KERNEL
50 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
61config USB_GADGET_DEBUG_FILES
62 boolean "Debugging information files (DEVELOPMENT)"
63 depends on PROC_FS
64 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
72config USB_GADGET_DEBUG_FS
73 boolean "Debugging information files in debugfs (DEVELOPMENT)"
74 depends on DEBUG_FS
75 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
83config 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
100config 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
116#
117# USB Peripheral Controller Support
118#
119# 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#
126menu "USB Peripheral Controller"
127
128#
129# Integrated controllers
130#
131
132config USB_AT91
133 tristate "Atmel AT91 USB Device Port"
134 depends on ARCH_AT91
135 help
136 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).
139
140 Say "y" to link the driver statically, or "m" to build a
141 dynamically linked module called "at91_udc" and force all
142 gadget drivers to also be dynamically linked.
143
144config 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
155config USB_ATMEL_USBA
156 tristate "Atmel USBA"
157 select USB_GADGET_DUALSPEED
158 depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
159 help
160 USBA is the integrated high-speed USB Device controller on
161 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
162
163config USB_FSL_USB2
164 tristate "Freescale Highspeed USB DR Peripheral Controller"
165 depends on FSL_SOC || ARCH_MXC
166 select USB_GADGET_DUALSPEED
167 select USB_FSL_MPH_DR_OF if OF
168 help
169 Some of Freescale PowerPC and i.MX processors have a High Speed
170 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
179config USB_FUSB300
180 tristate "Faraday FUSB300 USB Peripheral Controller"
181 depends on !PHYS_ADDR_T_64BIT
182 select USB_GADGET_DUALSPEED
183 help
184 Faraday usb device controller FUSB300 driver
185
186config USB_OMAP
187 tristate "OMAP USB Device Controller"
188 depends on ARCH_OMAP
189 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
190 select USB_OTG_UTILS if ARCH_OMAP
191 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
202config USB_PXA25X
203 tristate "PXA 25x or IXP 4xx"
204 depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
205 select USB_OTG_UTILS
206 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
218# 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
221 depends on USB_PXA25X
222 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
228config USB_R8A66597
229 tristate "Renesas R8A66597 USB Peripheral Controller"
230 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
240config USB_RENESAS_USBHS_UDC
241 tristate 'Renesas USBHS controller'
242 depends on USB_RENESAS_USBHS
243 select USB_GADGET_DUALSPEED
244 help
245 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.
248
249 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.
252
253config USB_PXA27X
254 tristate "PXA 27x"
255 depends on ARCH_PXA && (PXA27x || PXA3xx)
256 select USB_OTG_UTILS
257 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
268config USB_S3C_HSOTG
269 tristate "S3C HS/OtG USB Device controller"
270 depends on S3C_DEV_USB_HSOTG
271 select USB_GADGET_DUALSPEED
272 help
273 The Samsung S3C64XX USB2.0 high-speed gadget controller
274 integrated into the S3C64XX series SoC.
275
276config USB_IMX
277 tristate "Freescale i.MX1 USB Peripheral Controller"
278 depends on ARCH_MXC
279 help
280 Freescale's i.MX1 includes an integrated full speed
281 USB 1.1 device controller.
282
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
290config USB_S3C2410
291 tristate "S3C2410 USB Device Controller"
292 depends on ARCH_S3C24XX
293 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
301config USB_S3C2410_DEBUG
302 boolean "S3C2410 udc debug messages"
303 depends on USB_S3C2410
304
305config USB_S3C_HSUDC
306 tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
307 depends on ARCH_S3C24XX
308 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
316config USB_MV_UDC
317 tristate "Marvell USB2.0 Device Controller"
318 select USB_GADGET_DUALSPEED
319 help
320 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.
323
324#
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
330 tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
331 depends on USB_MUSB_HDRC
332 select USB_GADGET_DUALSPEED
333 help
334 This OTG-capable silicon IP is used in dual designs including
335 the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
336
337config USB_M66592
338 tristate "Renesas M66592 USB Peripheral Controller"
339 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.
344
345 Say "y" to link the driver statically, or "m" to build a
346 dynamically linked module called "m66592_udc" and force all
347 gadget drivers to also be dynamically linked.
348
349#
350# Controllers available only in discrete form (and all PCI controllers)
351#
352
353config USB_AMD5536UDC
354 tristate "AMD5536 UDC"
355 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
368config USB_FSL_QE
369 tristate "Freescale QE/CPM USB Device Controller"
370 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
379 dynamically linked module called "fsl_qe_udc".
380
381config USB_NET2272
382 tristate "PLX NET2272"
383 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
394config USB_NET2272_DMA
395 boolean "Support external DMA controller"
396 depends on USB_NET2272
397 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
404config USB_NET2280
405 tristate "NetChip 228x"
406 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
420config USB_GOKU
421 tristate "Toshiba TC86C001 'Goku-S'"
422 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
434config USB_EG20T
435 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
436 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
451 This driver also can be used for LAPIS Semiconductor's ML7213 which is
452 for IVI(In-Vehicle Infotainment) use.
453 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.
456
457#
458# LAST -- dummy/emulated controller
459#
460
461config USB_DUMMY_HCD
462 tristate "Dummy HCD (DEVELOPMENT)"
463 depends on USB=y || (USB=m && USB_GADGET=m)
464 select USB_GADGET_DUALSPEED
465 select USB_GADGET_SUPERSPEED
466 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.
472
473 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.
476
477 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
485# NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
486# first and will be selected by default.
487
488endmenu
489
490# Selected by UDC drivers that support high-speed operation.
491config USB_GADGET_DUALSPEED
492 bool
493
494# Selected by UDC drivers that support super-speed opperation
495config USB_GADGET_SUPERSPEED
496 bool
497 depends on USB_GADGET_DUALSPEED
498
499#
500# USB Gadget Drivers
501#
502choice
503 tristate "USB Gadget Drivers"
504 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)"
525 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
557config USB_AUDIO
558 tristate "Audio Gadget (EXPERIMENTAL)"
559 depends on SND
560 select SND_PCM
561 help
562 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.
573
574 Say "y" to link the driver statically, or "m" to build a
575 dynamically linked module called "g_audio".
576
577config 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
585config USB_ETH
586 tristate "Ethernet Gadget (with CDC Ethernet support)"
587 depends on NET
588 select CRC32
589 help
590 This driver implements Ethernet style communication, in one of
591 several ways:
592
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
601 - 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.
606
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
621 bool "RNDIS support"
622 depends on USB_ETH
623 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
638config 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
654config 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
661 of several ethernet frames into one USB transfer and different
662 alignment possibilities.
663
664 Say "y" to link the driver statically, or "m" to build a
665 dynamically linked module called "g_ncm".
666
667config 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
677 Currently, this option is still labelled as EXPERIMENTAL because
678 of existing race conditions in the underlying in-kernel AIO core.
679
680 Say "y" to link the driver statically, or "m" to build a
681 dynamically linked module called "gadgetfs".
682
683config USB_FUNCTIONFS
684 tristate "Function Filesystem (EXPERIMENTAL)"
685 depends on EXPERIMENTAL
686 select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
687 help
688 The Function Filesystem (FunctionFS) lets one create USB
689 composite functions in user space in the same way GadgetFS
690 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
695 If you say "y" or "m" here you will be able what kind of
696 configurations the gadget will provide.
697
698 Say "y" to link the driver statically, or "m" to build
699 a dynamically linked module called "g_ffs".
700
701config USB_FUNCTIONFS_ETH
702 bool "Include configuration with CDC ECM (Ethernet)"
703 depends on USB_FUNCTIONFS && NET
704 help
705 Include a configuration with CDC ECM function (Ethernet) and the
706 Function Filesystem.
707
708config USB_FUNCTIONFS_RNDIS
709 bool "Include configuration with RNDIS (Ethernet)"
710 depends on USB_FUNCTIONFS && NET
711 help
712 Include a configuration with RNDIS function (Ethernet) and the Filesystem.
713
714config USB_FUNCTIONFS_GENERIC
715 bool "Include 'pure' configuration"
716 depends on USB_FUNCTIONFS
717 help
718 Include a configuration with the Function Filesystem alone with
719 no Ethernet interface.
720
721config USB_FILE_STORAGE
722 tristate "File-backed Storage Gadget (DEPRECATED)"
723 depends on BLOCK
724 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
733 NOTE: This driver is deprecated. Its replacement is the
734 Mass Storage Gadget.
735
736config 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
746config 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
755 This driver is an updated replacement for the deprecated
756 File-backed Storage Gadget (g_file_storage).
757
758 Say "y" to link the driver statically, or "m" to build
759 a dynamically linked module called "g_mass_storage".
760
761config 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
771config USB_G_SERIAL
772 tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
773 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
779 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
783 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
788 make MS-Windows work with CDC ACM.
789
790config 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
804config 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.
818
819config USB_CDC_COMPOSITE
820 tristate "CDC Composite Device (Ethernet and ACM)"
821 depends on NET
822 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
833config 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
843config 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
853config USB_G_MULTI
854 tristate "Multifunction Composite Gadget (EXPERIMENTAL)"
855 depends on BLOCK && NET
856 select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
857 help
858 The Multifunction Composite Gadget provides Ethernet (RNDIS
859 and/or CDC Ethernet), mass storage and ACM serial link
860 interfaces.
861
862 You will be asked to choose which of the two configurations is
863 to be available in the gadget. At least one configuration must
864 be chosen to make the gadget usable. Selecting more than one
865 configuration will prevent Windows from automatically detecting
866 the gadget as a composite gadget, so an INF file will be needed to
867 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
879 Gadget. This is the configuration dedicated for Windows since RNDIS
880 is Microsoft's protocol.
881
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
891 Composite Gadget.
892
893 If unsure, say "y".
894
895config 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".
906
907config 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
935# put drivers that need isochronous transfer support (for audio
936# or video class gadget drivers), or specific hardware, here.
937config USB_G_WEBCAM
938 tristate "USB Webcam Gadget"
939 depends on VIDEO_DEV
940 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.
944
945 Say "y" to link the driver statically, or "m" to build a
946 dynamically linked module called "g_webcam".
947
948endchoice
949
950endif # USB_GADGET