2 # USB Gadget support on a system involves
3 # (a) a peripheral controller, and
4 # (b) the gadget driver using it.
6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
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.
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).
17 tristate "USB Gadget Support"
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.
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
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.)
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).
42 For more information, see <http://www.linux-usb.org/gadget> and
43 the kernel DocBook documentation for this API.
47 config USB_GADGET_DEBUG
48 boolean "Debugging messages (DEVELOPMENT)"
49 depends on DEBUG_KERNEL
51 Many controller and gadget drivers will print some debugging
52 messages if you use this option to ask for those messages.
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
61 config USB_GADGET_DEBUG_FILES
62 boolean "Debugging information files (DEVELOPMENT)"
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".
72 config USB_GADGET_DEBUG_FS
73 boolean "Debugging information files in debugfs (DEVELOPMENT)"
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".
83 config USB_GADGET_VBUS_DRAW
84 int "Maximum VBUS Power usage (2-500 mA)"
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.
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.
97 This value will be used except for system-specific gadget
98 drivers that have more specific information.
100 config USB_GADGET_STORAGE_NUM_BUFFERS
101 int "Number of storage pipeline buffers"
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.
117 # USB Peripheral Controller Support
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.
126 menu "USB Peripheral Controller"
129 # Integrated controllers
133 tristate "Atmel AT91 USB Device Port"
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).
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.
145 tristate "LPC32XX USB Peripheral Controller"
146 depends on ARCH_LPC32XX
149 This option selects the USB device controller in the LPC32xx SoC.
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.
155 config USB_ATMEL_USBA
156 tristate "Atmel USBA"
157 depends on AVR32 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
159 USBA is the integrated high-speed USB Device controller on
160 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
163 tristate "Freescale Highspeed USB DR Peripheral Controller"
164 depends on FSL_SOC || ARCH_MXC
165 select USB_FSL_MPH_DR_OF if OF
167 Some of Freescale PowerPC and i.MX processors have a High Speed
168 Dual-Role(DR) USB controller, which supports device mode.
170 The number of programmable endpoints is different through
173 Say "y" to link the driver statically, or "m" to build a
174 dynamically linked module called "fsl_usb2_udc" and force
175 all gadget drivers to also be dynamically linked.
178 tristate "Faraday FUSB300 USB Peripheral Controller"
179 depends on !PHYS_ADDR_T_64BIT
181 Faraday usb device controller FUSB300 driver
184 tristate "OMAP USB Device Controller"
185 depends on ARCH_OMAP1
186 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
187 select USB_OTG_UTILS if ARCH_OMAP
189 Many Texas Instruments OMAP processors have flexible full
190 speed USB device controllers, with support for up to 30
191 endpoints (plus endpoint zero). This driver supports the
192 controller in the OMAP 1611, and should work with controllers
193 in other OMAP processors too, given minor tweaks.
195 Say "y" to link the driver statically, or "m" to build a
196 dynamically linked module called "omap_udc" and force all
197 gadget drivers to also be dynamically linked.
200 tristate "PXA 25x or IXP 4xx"
201 depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
204 Intel's PXA 25x series XScale ARM-5TE processors include
205 an integrated full speed USB 1.1 device controller. The
206 controller in the IXP 4xx series is register-compatible.
208 It has fifteen fixed-function endpoints, as well as endpoint
209 zero (for control transfers).
211 Say "y" to link the driver statically, or "m" to build a
212 dynamically linked module called "pxa25x_udc" and force all
213 gadget drivers to also be dynamically linked.
215 # if there's only one gadget driver, using only two bulk endpoints,
216 # don't waste memory for the other endpoints
217 config USB_PXA25X_SMALL
218 depends on USB_PXA25X
220 default n if USB_ETH_RNDIS
221 default y if USB_ZERO
223 default y if USB_G_SERIAL
226 tristate "Renesas R8A66597 USB Peripheral Controller"
228 R8A66597 is a discrete USB host and peripheral controller chip that
229 supports both full and high speed USB 2.0 data transfers.
230 It has nine configurable endpoints, and endpoint zero.
232 Say "y" to link the driver statically, or "m" to build a
233 dynamically linked module called "r8a66597_udc" and force all
234 gadget drivers to also be dynamically linked.
236 config USB_RENESAS_USBHS_UDC
237 tristate 'Renesas USBHS controller'
238 depends on USB_RENESAS_USBHS
240 Renesas USBHS is a discrete USB host and peripheral controller chip
241 that supports both full and high speed USB 2.0 data transfers.
242 It has nine or more configurable endpoints, and endpoint zero.
244 Say "y" to link the driver statically, or "m" to build a
245 dynamically linked module called "renesas_usbhs" and force all
246 gadget drivers to also be dynamically linked.
250 depends on ARCH_PXA && (PXA27x || PXA3xx)
253 Intel's PXA 27x series XScale ARM v5TE processors include
254 an integrated full speed USB 1.1 device controller.
256 It has up to 23 endpoints, as well as endpoint zero (for
259 Say "y" to link the driver statically, or "m" to build a
260 dynamically linked module called "pxa27x_udc" and force all
261 gadget drivers to also be dynamically linked.
264 tristate "S3C HS/OtG USB Device controller"
265 depends on S3C_DEV_USB_HSOTG
267 The Samsung S3C64XX USB2.0 high-speed gadget controller
268 integrated into the S3C64XX series SoC.
271 tristate "Freescale i.MX1 USB Peripheral Controller"
274 Freescale's i.MX1 includes an integrated full speed
275 USB 1.1 device controller.
277 It has Six fixed-function endpoints, as well as endpoint
278 zero (for control transfers).
280 Say "y" to link the driver statically, or "m" to build a
281 dynamically linked module called "imx_udc" and force all
282 gadget drivers to also be dynamically linked.
285 tristate "S3C2410 USB Device Controller"
286 depends on ARCH_S3C24XX
288 Samsung's S3C2410 is an ARM-4 processor with an integrated
289 full speed USB 1.1 device controller. It has 4 configurable
290 endpoints, as well as endpoint zero (for control transfers).
292 This driver has been tested on the S3C2410, S3C2412, and
295 config USB_S3C2410_DEBUG
296 boolean "S3C2410 udc debug messages"
297 depends on USB_S3C2410
300 tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
301 depends on ARCH_S3C24XX
303 Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
304 integrated with dual speed USB 2.0 device controller. It has
305 8 endpoints, as well as endpoint zero.
307 This driver has been tested on S3C2416 and S3C2450 processors.
310 tristate "Marvell USB2.0 Device Controller"
312 Marvell Socs (including PXA and MMP series) include a high speed
313 USB2.0 OTG controller, which can be configured as high speed or
314 full speed USB peripheral.
317 tristate "MARVELL PXA2128 USB 3.0 controller"
319 select USB_GADGET_DUALSPEED
320 select USB_GADGET_SUPERSPEED
322 MARVELL PXA2128 Processor series include a super speed USB3.0 device
323 controller, which support super speed USB peripheral.
326 # Controllers available in both integrated and discrete versions
329 # musb builds in ../musb along with host support
330 config USB_GADGET_MUSB_HDRC
331 tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
332 depends on USB_MUSB_HDRC
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
338 tristate "Renesas M66592 USB Peripheral Controller"
340 M66592 is a discrete USB peripheral controller chip that
341 supports both full and high speed USB 2.0 data transfers.
342 It has seven configurable endpoints, and endpoint zero.
344 Say "y" to link the driver statically, or "m" to build a
345 dynamically linked module called "m66592_udc" and force all
346 gadget drivers to also be dynamically linked.
349 # Controllers available only in discrete form (and all PCI controllers)
352 config USB_AMD5536UDC
353 tristate "AMD5536 UDC"
356 The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
357 It is a USB Highspeed DMA capable USB device controller. Beside ep0
358 it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
359 The UDC port supports OTG operation, and may be used as a host port
360 if it's not being used to implement peripheral or OTG roles.
362 Say "y" to link the driver statically, or "m" to build a
363 dynamically linked module called "amd5536udc" and force all
364 gadget drivers to also be dynamically linked.
367 tristate "Freescale QE/CPM USB Device Controller"
368 depends on FSL_SOC && (QUICC_ENGINE || CPM)
370 Some of Freescale PowerPC processors have a Full Speed
371 QE/CPM2 USB controller, which support device mode with 4
372 programmable endpoints. This driver supports the
373 controller in the MPC8360 and MPC8272, and should work with
374 controllers having QE or CPM2, given minor tweaks.
376 Set CONFIG_USB_GADGET to "m" to build this driver as a
377 dynamically linked module called "fsl_qe_udc".
380 tristate "PLX NET2272"
382 PLX NET2272 is a USB peripheral controller which supports
383 both full and high speed USB 2.0 data transfers.
385 It has three configurable endpoints, as well as endpoint zero
386 (for control transfer).
387 Say "y" to link the driver statically, or "m" to build a
388 dynamically linked module called "net2272" and force all
389 gadget drivers to also be dynamically linked.
391 config USB_NET2272_DMA
392 boolean "Support external DMA controller"
393 depends on USB_NET2272
395 The NET2272 part can optionally support an external DMA
396 controller, but your board has to have support in the
399 If unsure, say "N" here. The driver works fine in PIO mode.
402 tristate "NetChip 228x"
405 NetChip 2280 / 2282 is a PCI based USB peripheral controller which
406 supports both full and high speed USB 2.0 data transfers.
408 It has six configurable endpoints, as well as endpoint zero
409 (for control transfers) and several endpoints with dedicated
412 Say "y" to link the driver statically, or "m" to build a
413 dynamically linked module called "net2280" and force all
414 gadget drivers to also be dynamically linked.
417 tristate "Toshiba TC86C001 'Goku-S'"
420 The Toshiba TC86C001 is a PCI device which includes controllers
421 for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
423 The device controller has three configurable (bulk or interrupt)
424 endpoints, plus endpoint zero (for control transfers).
426 Say "y" to link the driver statically, or "m" to build a
427 dynamically linked module called "goku_udc" and to force all
428 gadget drivers to also be dynamically linked.
431 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
434 This is a USB device driver for EG20T PCH.
435 EG20T PCH is the platform controller hub that is used in Intel's
436 general embedded platform. EG20T PCH has USB device interface.
437 Using this interface, it is able to access system devices connected
439 This driver enables USB device function.
440 USB device is a USB peripheral controller which
441 supports both full and high speed USB 2.0 data transfers.
442 This driver supports both control transfer and bulk transfer modes.
443 This driver dose not support interrupt transfer or isochronous
446 This driver also can be used for LAPIS Semiconductor's ML7213 which is
447 for IVI(In-Vehicle Infotainment) use.
448 ML7831 is for general purpose use.
449 ML7213/ML7831 is companion chip for Intel Atom E6xx series.
450 ML7213/ML7831 is completely compatible for Intel EG20T PCH.
453 # LAST -- dummy/emulated controller
457 tristate "Dummy HCD (DEVELOPMENT)"
458 depends on USB=y || (USB=m && USB_GADGET=m)
460 This host controller driver emulates USB, looping all data transfer
461 requests back to a USB "gadget driver" in the same host. The host
462 side is the master; the gadget side is the slave. Gadget drivers
463 can be high, full, or low speed; and they have access to endpoints
464 like those from NET2280, PXA2xx, or SA1100 hardware.
466 This may help in some stages of creating a driver to embed in a
467 Linux device, since it lets you debug several parts of the gadget
468 driver without its hardware or drivers being involved.
470 Since such a gadget side driver needs to interoperate with a host
471 side Linux-USB device driver, this may help to debug both sides
472 of a USB protocol stack.
474 Say "y" to link the driver statically, or "m" to build a
475 dynamically linked module called "dummy_hcd" and force all
476 gadget drivers to also be dynamically linked.
478 # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
479 # first and will be selected by default.
487 tristate "USB Gadget Drivers"
490 A Linux "Gadget Driver" talks to the USB Peripheral Controller
491 driver through the abstract "gadget" API. Some other operating
492 systems call these "client" drivers, of which "class drivers"
493 are a subset (implementing a USB device class specification).
494 A gadget driver implements one or more USB functions using
495 the peripheral hardware.
497 Gadget drivers are hardware-neutral, or "platform independent",
498 except that they sometimes must understand quirks or limitations
499 of the particular controllers they work with. For example, when
500 a controller doesn't support alternate configurations or provide
501 enough of the right types of endpoints, the gadget driver might
502 not be able work with that controller, or might need to implement
503 a less common variant of a device class protocol.
505 # this first set of drivers all depend on bulk-capable hardware.
508 tristate "Gadget Zero (DEVELOPMENT)"
510 Gadget Zero is a two-configuration device. It either sinks and
511 sources bulk data; or it loops back a configurable number of
512 transfers. It also implements control requests, for "chapter 9"
513 conformance. The driver needs only two bulk-capable endpoints, so
514 it can work on top of most device-side usb controllers. It's
515 useful for testing, and is also a working example showing how
516 USB "gadget drivers" can be written.
518 Make this be the first driver you try using on top of any new
519 USB peripheral controller driver. Then you can use host-side
520 test software, like the "usbtest" driver, to put your hardware
521 and its driver through a basic set of functional tests.
523 Gadget Zero also works with the host-side "usb-skeleton" driver,
524 and with many kinds of host-side test software. You may need
525 to tweak product and vendor IDs before host software knows about
526 this device, and arrange to select an appropriate configuration.
528 Say "y" to link the driver statically, or "m" to build a
529 dynamically linked module called "g_zero".
531 config USB_ZERO_HNPTEST
532 boolean "HNP Test Device"
533 depends on USB_ZERO && USB_OTG
535 You can configure this device to enumerate using the device
536 identifiers of the USB-OTG test device. That means that when
537 this gadget connects to another OTG device, with this one using
538 the "B-Peripheral" role, that device will use HNP to let this
539 one serve as the USB host instead (in the "B-Host" role).
542 tristate "Audio Gadget (EXPERIMENTAL)"
546 This Gadget Audio driver is compatible with USB Audio Class
547 specification 2.0. It implements 1 AudioControl interface,
548 1 AudioStreaming Interface each for USB-OUT and USB-IN.
549 Number of channels, sample rate and sample size can be
550 specified as module parameters.
551 This driver doesn't expect any real Audio codec to be present
552 on the device - the audio streams are simply sinked to and
553 sourced from a virtual ALSA sound card created. The user-space
554 application may choose to do whatever it wants with the data
555 received from the USB Host and choose to provide whatever it
556 wants as audio data to the USB Host.
558 Say "y" to link the driver statically, or "m" to build a
559 dynamically linked module called "g_audio".
562 bool "UAC 1.0 (Legacy)"
565 If you instead want older UAC Spec-1.0 driver that also has audio
566 paths hardwired to the Audio codec chip on-board and doesn't work
570 tristate "Ethernet Gadget (with CDC Ethernet support)"
574 This driver implements Ethernet style communication, in one of
577 - The "Communication Device Class" (CDC) Ethernet Control Model.
578 That protocol is often avoided with pure Ethernet adapters, in
579 favor of simpler vendor-specific hardware, but is widely
580 supported by firmware for smart network devices.
582 - On hardware can't implement that protocol, a simple CDC subset
583 is used, placing fewer demands on USB.
585 - CDC Ethernet Emulation Model (EEM) is a newer standard that has
586 a simpler interface that can be used by more USB hardware.
588 RNDIS support is an additional option, more demanding than than
591 Within the USB device, this gadget driver exposes a network device
592 "usbX", where X depends on what other networking devices you have.
593 Treat it like a two-node Ethernet link: host, and gadget.
595 The Linux-USB host-side "usbnet" driver interoperates with this
596 driver, so that deep I/O queues can be supported. On 2.4 kernels,
597 use "CDCEther" instead, if you're using the CDC option. That CDC
598 mode should also interoperate with standard CDC Ethernet class
599 drivers on other host operating systems.
601 Say "y" to link the driver statically, or "m" to build a
602 dynamically linked module called "g_ether".
609 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
610 and Microsoft provides redistributable binary RNDIS drivers for
611 older versions of Windows.
613 If you say "y" here, the Ethernet gadget driver will try to provide
614 a second device configuration, supporting RNDIS to talk to such
617 To make MS-Windows work with this, use Documentation/usb/linux.inf
618 as the "driver info file". For versions of MS-Windows older than
619 XP, you'll need to download drivers from Microsoft's website; a URL
620 is given in comments found in that info file.
623 bool "Ethernet Emulation Model (EEM) support"
627 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
628 and therefore can be supported by more hardware. Technically ECM and
629 EEM are designed for different applications. The ECM model extends
630 the network interface to the target (e.g. a USB cable modem), and the
631 EEM model is for mobile devices to communicate with hosts using
632 ethernet over USB. For Linux gadgets, however, the interface with
633 the host is the same (a usbX device), so the differences are minimal.
635 If you say "y" here, the Ethernet gadget driver will use the EEM
636 protocol rather than ECM. If unsure, say "n".
639 tristate "Network Control Model (NCM) support"
643 This driver implements USB CDC NCM subclass standard. NCM is
644 an advanced protocol for Ethernet encapsulation, allows grouping
645 of several ethernet frames into one USB transfer and different
646 alignment possibilities.
648 Say "y" to link the driver statically, or "m" to build a
649 dynamically linked module called "g_ncm".
652 tristate "Gadget Filesystem (EXPERIMENTAL)"
653 depends on EXPERIMENTAL
655 This driver provides a filesystem based API that lets user mode
656 programs implement a single-configuration USB device, including
657 endpoint I/O and control requests that don't relate to enumeration.
658 All endpoints, transfer speeds, and transfer types supported by
659 the hardware are available, through read() and write() calls.
661 Currently, this option is still labelled as EXPERIMENTAL because
662 of existing race conditions in the underlying in-kernel AIO core.
664 Say "y" to link the driver statically, or "m" to build a
665 dynamically linked module called "gadgetfs".
667 config USB_FUNCTIONFS
668 tristate "Function Filesystem (EXPERIMENTAL)"
669 depends on EXPERIMENTAL
670 select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
672 The Function Filesystem (FunctionFS) lets one create USB
673 composite functions in user space in the same way GadgetFS
674 lets one create USB gadgets in user space. This allows creation
675 of composite gadgets such that some of the functions are
676 implemented in kernel space (for instance Ethernet, serial or
677 mass storage) and other are implemented in user space.
679 If you say "y" or "m" here you will be able what kind of
680 configurations the gadget will provide.
682 Say "y" to link the driver statically, or "m" to build
683 a dynamically linked module called "g_ffs".
685 config USB_FUNCTIONFS_ETH
686 bool "Include configuration with CDC ECM (Ethernet)"
687 depends on USB_FUNCTIONFS && NET
689 Include a configuration with CDC ECM function (Ethernet) and the
692 config USB_FUNCTIONFS_RNDIS
693 bool "Include configuration with RNDIS (Ethernet)"
694 depends on USB_FUNCTIONFS && NET
696 Include a configuration with RNDIS function (Ethernet) and the Filesystem.
698 config USB_FUNCTIONFS_GENERIC
699 bool "Include 'pure' configuration"
700 depends on USB_FUNCTIONFS
702 Include a configuration with the Function Filesystem alone with
703 no Ethernet interface.
705 config USB_FILE_STORAGE
706 tristate "File-backed Storage Gadget (DEPRECATED)"
709 The File-backed Storage Gadget acts as a USB Mass Storage
710 disk drive. As its storage repository it can use a regular
711 file or a block device (in much the same way as the "loop"
712 device driver), specified as a module parameter.
714 Say "y" to link the driver statically, or "m" to build a
715 dynamically linked module called "g_file_storage".
717 NOTE: This driver is deprecated. Its replacement is the
720 config USB_FILE_STORAGE_TEST
721 bool "File-backed Storage Gadget testing version"
722 depends on USB_FILE_STORAGE
725 Say "y" to generate the larger testing version of the
726 File-backed Storage Gadget, useful for probing the
727 behavior of USB Mass Storage hosts. Not needed for
730 config USB_MASS_STORAGE
731 tristate "Mass Storage Gadget"
734 The Mass Storage Gadget acts as a USB Mass Storage disk drive.
735 As its storage repository it can use a regular file or a block
736 device (in much the same way as the "loop" device driver),
737 specified as a module parameter or sysfs option.
739 This driver is an updated replacement for the deprecated
740 File-backed Storage Gadget (g_file_storage).
742 Say "y" to link the driver statically, or "m" to build
743 a dynamically linked module called "g_mass_storage".
745 config USB_GADGET_TARGET
746 tristate "USB Gadget Target Fabric Module"
747 depends on TARGET_CORE
749 This fabric is an USB gadget. Two USB protocols are supported that is
750 BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
751 advertised on alternative interface 0 (primary) and UAS is on
752 alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
753 UAS utilizes the USB 3.0 feature called streams support.
756 tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
758 The Serial Gadget talks to the Linux-USB generic serial driver.
759 This driver supports a CDC-ACM module option, which can be used
760 to interoperate with MS-Windows hosts or with the Linux-USB
763 This driver also supports a CDC-OBEX option. You will need a
764 user space OBEX server talking to /dev/ttyGS*, since the kernel
765 itself doesn't implement the OBEX protocol.
767 Say "y" to link the driver statically, or "m" to build a
768 dynamically linked module called "g_serial".
770 For more information, see Documentation/usb/gadget_serial.txt
771 which includes instructions and a "driver info file" needed to
772 make MS-Windows work with CDC ACM.
774 config USB_MIDI_GADGET
775 tristate "MIDI Gadget (EXPERIMENTAL)"
776 depends on SND && EXPERIMENTAL
779 The MIDI Gadget acts as a USB Audio device, with one MIDI
780 input and one MIDI output. These MIDI jacks appear as
781 a sound "card" in the ALSA sound system. Other MIDI
782 connections can then be made on the gadget system, using
783 ALSA's aconnect utility etc.
785 Say "y" to link the driver statically, or "m" to build a
786 dynamically linked module called "g_midi".
789 tristate "Printer Gadget"
791 The Printer Gadget channels data between the USB host and a
792 userspace program driving the print engine. The user space
793 program reads and writes the device file /dev/g_printer to
794 receive or send printer data. It can use ioctl calls to
795 the device file to get or set printer status.
797 Say "y" to link the driver statically, or "m" to build a
798 dynamically linked module called "g_printer".
800 For more information, see Documentation/usb/gadget_printer.txt
801 which includes sample code for accessing the device file.
803 config USB_CDC_COMPOSITE
804 tristate "CDC Composite Device (Ethernet and ACM)"
807 This driver provides two functions in one configuration:
808 a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
810 This driver requires four bulk and two interrupt endpoints,
811 plus the ability to handle altsettings. Not all peripheral
812 controllers are that capable.
814 Say "y" to link the driver statically, or "m" to build a
815 dynamically linked module.
818 tristate "Nokia composite gadget"
821 The Nokia composite gadget provides support for acm, obex
822 and phonet in only one composite gadget driver.
824 It's only really useful for N900 hardware. If you're building
825 a kernel for N900, say Y or M here. If unsure, say N.
828 tristate "CDC Composite Device (ACM and mass storage)"
831 This driver provides two functions in one configuration:
832 a mass storage, and a CDC ACM (serial port) link.
834 Say "y" to link the driver statically, or "m" to build a
835 dynamically linked module called "g_acm_ms".
838 tristate "Multifunction Composite Gadget (EXPERIMENTAL)"
839 depends on BLOCK && NET
840 select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
842 The Multifunction Composite Gadget provides Ethernet (RNDIS
843 and/or CDC Ethernet), mass storage and ACM serial link
846 You will be asked to choose which of the two configurations is
847 to be available in the gadget. At least one configuration must
848 be chosen to make the gadget usable. Selecting more than one
849 configuration will prevent Windows from automatically detecting
850 the gadget as a composite gadget, so an INF file will be needed to
853 Say "y" to link the driver statically, or "m" to build a
854 dynamically linked module called "g_multi".
856 config USB_G_MULTI_RNDIS
857 bool "RNDIS + CDC Serial + Storage configuration"
858 depends on USB_G_MULTI
861 This option enables a configuration with RNDIS, CDC Serial and
862 Mass Storage functions available in the Multifunction Composite
863 Gadget. This is the configuration dedicated for Windows since RNDIS
864 is Microsoft's protocol.
868 config USB_G_MULTI_CDC
869 bool "CDC Ethernet + CDC Serial + Storage configuration"
870 depends on USB_G_MULTI
873 This option enables a configuration with CDC Ethernet (ECM), CDC
874 Serial and Mass Storage functions available in the Multifunction
880 tristate "HID Gadget"
882 The HID gadget driver provides generic emulation of USB
883 Human Interface Devices (HID).
885 For more information, see Documentation/usb/gadget_hid.txt which
886 includes sample code for accessing the device files.
888 Say "y" to link the driver statically, or "m" to build a
889 dynamically linked module called "g_hid".
892 tristate "EHCI Debug Device Gadget"
894 This gadget emulates an EHCI Debug device. This is useful when you want
895 to interact with an EHCI Debug Port.
897 Say "y" to link the driver statically, or "m" to build a
898 dynamically linked module called "g_dbgp".
902 prompt "EHCI Debug Device mode"
903 default USB_G_DBGP_SERIAL
905 config USB_G_DBGP_PRINTK
906 depends on USB_G_DBGP
909 Directly printk() received data. No interaction.
911 config USB_G_DBGP_SERIAL
912 depends on USB_G_DBGP
915 Userland can interact using /dev/ttyGSxxx.
919 # put drivers that need isochronous transfer support (for audio
920 # or video class gadget drivers), or specific hardware, here.
922 tristate "USB Webcam Gadget"
925 The Webcam Gadget acts as a composite USB Audio and Video Class
926 device. It provides a userspace API to process UVC control requests
927 and stream video data to the host.
929 Say "y" to link the driver statically, or "m" to build a
930 dynamically linked module called "g_webcam".