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.
162 config USB_BCM63XX_UDC
163 tristate "Broadcom BCM63xx Peripheral Controller"
166 Many Broadcom BCM63xx chipsets (such as the BCM6328) have a
167 high speed USB Device Port with support for four fixed endpoints
168 (plus endpoint zero).
170 Say "y" to link the driver statically, or "m" to build a
171 dynamically linked module called "bcm63xx_udc".
174 tristate "Freescale Highspeed USB DR Peripheral Controller"
175 depends on FSL_SOC || ARCH_MXC
176 select USB_FSL_MPH_DR_OF if OF
178 Some of Freescale PowerPC and i.MX processors have a High Speed
179 Dual-Role(DR) USB controller, which supports device mode.
181 The number of programmable endpoints is different through
184 Say "y" to link the driver statically, or "m" to build a
185 dynamically linked module called "fsl_usb2_udc" and force
186 all gadget drivers to also be dynamically linked.
189 tristate "Faraday FUSB300 USB Peripheral Controller"
190 depends on !PHYS_ADDR_T_64BIT
192 Faraday usb device controller FUSB300 driver
195 tristate "OMAP USB Device Controller"
196 depends on ARCH_OMAP1
197 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
198 select USB_OTG_UTILS if ARCH_OMAP
200 Many Texas Instruments OMAP processors have flexible full
201 speed USB device controllers, with support for up to 30
202 endpoints (plus endpoint zero). This driver supports the
203 controller in the OMAP 1611, and should work with controllers
204 in other OMAP processors too, given minor tweaks.
206 Say "y" to link the driver statically, or "m" to build a
207 dynamically linked module called "omap_udc" and force all
208 gadget drivers to also be dynamically linked.
211 tristate "PXA 25x or IXP 4xx"
212 depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
215 Intel's PXA 25x series XScale ARM-5TE processors include
216 an integrated full speed USB 1.1 device controller. The
217 controller in the IXP 4xx series is register-compatible.
219 It has fifteen fixed-function endpoints, as well as endpoint
220 zero (for control transfers).
222 Say "y" to link the driver statically, or "m" to build a
223 dynamically linked module called "pxa25x_udc" and force all
224 gadget drivers to also be dynamically linked.
226 # if there's only one gadget driver, using only two bulk endpoints,
227 # don't waste memory for the other endpoints
228 config USB_PXA25X_SMALL
229 depends on USB_PXA25X
231 default n if USB_ETH_RNDIS
232 default y if USB_ZERO
234 default y if USB_G_SERIAL
237 tristate "Renesas R8A66597 USB Peripheral Controller"
239 R8A66597 is a discrete USB host and peripheral controller chip that
240 supports both full and high speed USB 2.0 data transfers.
241 It has nine configurable endpoints, and endpoint zero.
243 Say "y" to link the driver statically, or "m" to build a
244 dynamically linked module called "r8a66597_udc" and force all
245 gadget drivers to also be dynamically linked.
247 config USB_RENESAS_USBHS_UDC
248 tristate 'Renesas USBHS controller'
249 depends on USB_RENESAS_USBHS
251 Renesas USBHS is a discrete USB host and peripheral controller chip
252 that supports both full and high speed USB 2.0 data transfers.
253 It has nine or more configurable endpoints, and endpoint zero.
255 Say "y" to link the driver statically, or "m" to build a
256 dynamically linked module called "renesas_usbhs" and force all
257 gadget drivers to also be dynamically linked.
261 depends on ARCH_PXA && (PXA27x || PXA3xx)
264 Intel's PXA 27x series XScale ARM v5TE processors include
265 an integrated full speed USB 1.1 device controller.
267 It has up to 23 endpoints, as well as endpoint zero (for
270 Say "y" to link the driver statically, or "m" to build a
271 dynamically linked module called "pxa27x_udc" and force all
272 gadget drivers to also be dynamically linked.
275 tristate "S3C HS/OtG USB Device controller"
276 depends on S3C_DEV_USB_HSOTG
278 The Samsung S3C64XX USB2.0 high-speed gadget controller
279 integrated into the S3C64XX series SoC.
282 tristate "Freescale i.MX1 USB Peripheral Controller"
285 Freescale's i.MX1 includes an integrated full speed
286 USB 1.1 device controller.
288 It has Six fixed-function endpoints, as well as endpoint
289 zero (for control transfers).
291 Say "y" to link the driver statically, or "m" to build a
292 dynamically linked module called "imx_udc" and force all
293 gadget drivers to also be dynamically linked.
296 tristate "S3C2410 USB Device Controller"
297 depends on ARCH_S3C24XX
299 Samsung's S3C2410 is an ARM-4 processor with an integrated
300 full speed USB 1.1 device controller. It has 4 configurable
301 endpoints, as well as endpoint zero (for control transfers).
303 This driver has been tested on the S3C2410, S3C2412, and
306 config USB_S3C2410_DEBUG
307 boolean "S3C2410 udc debug messages"
308 depends on USB_S3C2410
311 tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
312 depends on ARCH_S3C24XX
314 Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
315 integrated with dual speed USB 2.0 device controller. It has
316 8 endpoints, as well as endpoint zero.
318 This driver has been tested on S3C2416 and S3C2450 processors.
321 tristate "Marvell USB2.0 Device Controller"
323 Marvell Socs (including PXA and MMP series) include a high speed
324 USB2.0 OTG controller, which can be configured as high speed or
325 full speed USB peripheral.
328 tristate "MARVELL PXA2128 USB 3.0 controller"
330 select USB_GADGET_DUALSPEED
331 select USB_GADGET_SUPERSPEED
333 MARVELL PXA2128 Processor series include a super speed USB3.0 device
334 controller, which support super speed USB peripheral.
337 # Controllers available in both integrated and discrete versions
340 # musb builds in ../musb along with host support
341 config USB_GADGET_MUSB_HDRC
342 tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
343 depends on USB_MUSB_HDRC
345 This OTG-capable silicon IP is used in dual designs including
346 the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
349 tristate "Renesas M66592 USB Peripheral Controller"
351 M66592 is a discrete USB peripheral controller chip that
352 supports both full and high speed USB 2.0 data transfers.
353 It has seven configurable endpoints, and endpoint zero.
355 Say "y" to link the driver statically, or "m" to build a
356 dynamically linked module called "m66592_udc" and force all
357 gadget drivers to also be dynamically linked.
360 # Controllers available only in discrete form (and all PCI controllers)
363 config USB_AMD5536UDC
364 tristate "AMD5536 UDC"
367 The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
368 It is a USB Highspeed DMA capable USB device controller. Beside ep0
369 it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
370 The UDC port supports OTG operation, and may be used as a host port
371 if it's not being used to implement peripheral or OTG roles.
373 Say "y" to link the driver statically, or "m" to build a
374 dynamically linked module called "amd5536udc" and force all
375 gadget drivers to also be dynamically linked.
378 tristate "Freescale QE/CPM USB Device Controller"
379 depends on FSL_SOC && (QUICC_ENGINE || CPM)
381 Some of Freescale PowerPC processors have a Full Speed
382 QE/CPM2 USB controller, which support device mode with 4
383 programmable endpoints. This driver supports the
384 controller in the MPC8360 and MPC8272, and should work with
385 controllers having QE or CPM2, given minor tweaks.
387 Set CONFIG_USB_GADGET to "m" to build this driver as a
388 dynamically linked module called "fsl_qe_udc".
391 tristate "PLX NET2272"
393 PLX NET2272 is a USB peripheral controller which supports
394 both full and high speed USB 2.0 data transfers.
396 It has three configurable endpoints, as well as endpoint zero
397 (for control transfer).
398 Say "y" to link the driver statically, or "m" to build a
399 dynamically linked module called "net2272" and force all
400 gadget drivers to also be dynamically linked.
402 config USB_NET2272_DMA
403 boolean "Support external DMA controller"
404 depends on USB_NET2272
406 The NET2272 part can optionally support an external DMA
407 controller, but your board has to have support in the
410 If unsure, say "N" here. The driver works fine in PIO mode.
413 tristate "NetChip 228x"
416 NetChip 2280 / 2282 is a PCI based USB peripheral controller which
417 supports both full and high speed USB 2.0 data transfers.
419 It has six configurable endpoints, as well as endpoint zero
420 (for control transfers) and several endpoints with dedicated
423 Say "y" to link the driver statically, or "m" to build a
424 dynamically linked module called "net2280" and force all
425 gadget drivers to also be dynamically linked.
428 tristate "Toshiba TC86C001 'Goku-S'"
431 The Toshiba TC86C001 is a PCI device which includes controllers
432 for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
434 The device controller has three configurable (bulk or interrupt)
435 endpoints, plus endpoint zero (for control transfers).
437 Say "y" to link the driver statically, or "m" to build a
438 dynamically linked module called "goku_udc" and to force all
439 gadget drivers to also be dynamically linked.
442 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7213/ML7831) UDC"
445 This is a USB device driver for EG20T PCH.
446 EG20T PCH is the platform controller hub that is used in Intel's
447 general embedded platform. EG20T PCH has USB device interface.
448 Using this interface, it is able to access system devices connected
450 This driver enables USB device function.
451 USB device is a USB peripheral controller which
452 supports both full and high speed USB 2.0 data transfers.
453 This driver supports both control transfer and bulk transfer modes.
454 This driver dose not support interrupt transfer or isochronous
457 This driver also can be used for LAPIS Semiconductor's ML7213 which is
458 for IVI(In-Vehicle Infotainment) use.
459 ML7831 is for general purpose use.
460 ML7213/ML7831 is companion chip for Intel Atom E6xx series.
461 ML7213/ML7831 is completely compatible for Intel EG20T PCH.
464 # LAST -- dummy/emulated controller
468 tristate "Dummy HCD (DEVELOPMENT)"
469 depends on USB=y || (USB=m && USB_GADGET=m)
471 This host controller driver emulates USB, looping all data transfer
472 requests back to a USB "gadget driver" in the same host. The host
473 side is the master; the gadget side is the slave. Gadget drivers
474 can be high, full, or low speed; and they have access to endpoints
475 like those from NET2280, PXA2xx, or SA1100 hardware.
477 This may help in some stages of creating a driver to embed in a
478 Linux device, since it lets you debug several parts of the gadget
479 driver without its hardware or drivers being involved.
481 Since such a gadget side driver needs to interoperate with a host
482 side Linux-USB device driver, this may help to debug both sides
483 of a USB protocol stack.
485 Say "y" to link the driver statically, or "m" to build a
486 dynamically linked module called "dummy_hcd" and force all
487 gadget drivers to also be dynamically linked.
489 # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
490 # first and will be selected by default.
498 tristate "USB Gadget Drivers"
501 A Linux "Gadget Driver" talks to the USB Peripheral Controller
502 driver through the abstract "gadget" API. Some other operating
503 systems call these "client" drivers, of which "class drivers"
504 are a subset (implementing a USB device class specification).
505 A gadget driver implements one or more USB functions using
506 the peripheral hardware.
508 Gadget drivers are hardware-neutral, or "platform independent",
509 except that they sometimes must understand quirks or limitations
510 of the particular controllers they work with. For example, when
511 a controller doesn't support alternate configurations or provide
512 enough of the right types of endpoints, the gadget driver might
513 not be able work with that controller, or might need to implement
514 a less common variant of a device class protocol.
516 # this first set of drivers all depend on bulk-capable hardware.
519 tristate "Gadget Zero (DEVELOPMENT)"
521 Gadget Zero is a two-configuration device. It either sinks and
522 sources bulk data; or it loops back a configurable number of
523 transfers. It also implements control requests, for "chapter 9"
524 conformance. The driver needs only two bulk-capable endpoints, so
525 it can work on top of most device-side usb controllers. It's
526 useful for testing, and is also a working example showing how
527 USB "gadget drivers" can be written.
529 Make this be the first driver you try using on top of any new
530 USB peripheral controller driver. Then you can use host-side
531 test software, like the "usbtest" driver, to put your hardware
532 and its driver through a basic set of functional tests.
534 Gadget Zero also works with the host-side "usb-skeleton" driver,
535 and with many kinds of host-side test software. You may need
536 to tweak product and vendor IDs before host software knows about
537 this device, and arrange to select an appropriate configuration.
539 Say "y" to link the driver statically, or "m" to build a
540 dynamically linked module called "g_zero".
542 config USB_ZERO_HNPTEST
543 boolean "HNP Test Device"
544 depends on USB_ZERO && USB_OTG
546 You can configure this device to enumerate using the device
547 identifiers of the USB-OTG test device. That means that when
548 this gadget connects to another OTG device, with this one using
549 the "B-Peripheral" role, that device will use HNP to let this
550 one serve as the USB host instead (in the "B-Host" role).
553 tristate "Audio Gadget (EXPERIMENTAL)"
557 This Gadget Audio driver is compatible with USB Audio Class
558 specification 2.0. It implements 1 AudioControl interface,
559 1 AudioStreaming Interface each for USB-OUT and USB-IN.
560 Number of channels, sample rate and sample size can be
561 specified as module parameters.
562 This driver doesn't expect any real Audio codec to be present
563 on the device - the audio streams are simply sinked to and
564 sourced from a virtual ALSA sound card created. The user-space
565 application may choose to do whatever it wants with the data
566 received from the USB Host and choose to provide whatever it
567 wants as audio data to the USB Host.
569 Say "y" to link the driver statically, or "m" to build a
570 dynamically linked module called "g_audio".
573 bool "UAC 1.0 (Legacy)"
576 If you instead want older UAC Spec-1.0 driver that also has audio
577 paths hardwired to the Audio codec chip on-board and doesn't work
581 tristate "Ethernet Gadget (with CDC Ethernet support)"
585 This driver implements Ethernet style communication, in one of
588 - The "Communication Device Class" (CDC) Ethernet Control Model.
589 That protocol is often avoided with pure Ethernet adapters, in
590 favor of simpler vendor-specific hardware, but is widely
591 supported by firmware for smart network devices.
593 - On hardware can't implement that protocol, a simple CDC subset
594 is used, placing fewer demands on USB.
596 - CDC Ethernet Emulation Model (EEM) is a newer standard that has
597 a simpler interface that can be used by more USB hardware.
599 RNDIS support is an additional option, more demanding than than
602 Within the USB device, this gadget driver exposes a network device
603 "usbX", where X depends on what other networking devices you have.
604 Treat it like a two-node Ethernet link: host, and gadget.
606 The Linux-USB host-side "usbnet" driver interoperates with this
607 driver, so that deep I/O queues can be supported. On 2.4 kernels,
608 use "CDCEther" instead, if you're using the CDC option. That CDC
609 mode should also interoperate with standard CDC Ethernet class
610 drivers on other host operating systems.
612 Say "y" to link the driver statically, or "m" to build a
613 dynamically linked module called "g_ether".
620 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
621 and Microsoft provides redistributable binary RNDIS drivers for
622 older versions of Windows.
624 If you say "y" here, the Ethernet gadget driver will try to provide
625 a second device configuration, supporting RNDIS to talk to such
628 To make MS-Windows work with this, use Documentation/usb/linux.inf
629 as the "driver info file". For versions of MS-Windows older than
630 XP, you'll need to download drivers from Microsoft's website; a URL
631 is given in comments found in that info file.
634 bool "Ethernet Emulation Model (EEM) support"
638 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
639 and therefore can be supported by more hardware. Technically ECM and
640 EEM are designed for different applications. The ECM model extends
641 the network interface to the target (e.g. a USB cable modem), and the
642 EEM model is for mobile devices to communicate with hosts using
643 ethernet over USB. For Linux gadgets, however, the interface with
644 the host is the same (a usbX device), so the differences are minimal.
646 If you say "y" here, the Ethernet gadget driver will use the EEM
647 protocol rather than ECM. If unsure, say "n".
650 tristate "Network Control Model (NCM) support"
654 This driver implements USB CDC NCM subclass standard. NCM is
655 an advanced protocol for Ethernet encapsulation, allows grouping
656 of several ethernet frames into one USB transfer and different
657 alignment possibilities.
659 Say "y" to link the driver statically, or "m" to build a
660 dynamically linked module called "g_ncm".
663 tristate "Gadget Filesystem (EXPERIMENTAL)"
664 depends on EXPERIMENTAL
666 This driver provides a filesystem based API that lets user mode
667 programs implement a single-configuration USB device, including
668 endpoint I/O and control requests that don't relate to enumeration.
669 All endpoints, transfer speeds, and transfer types supported by
670 the hardware are available, through read() and write() calls.
672 Currently, this option is still labelled as EXPERIMENTAL because
673 of existing race conditions in the underlying in-kernel AIO core.
675 Say "y" to link the driver statically, or "m" to build a
676 dynamically linked module called "gadgetfs".
678 config USB_FUNCTIONFS
679 tristate "Function Filesystem (EXPERIMENTAL)"
680 depends on EXPERIMENTAL
681 select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
683 The Function Filesystem (FunctionFS) lets one create USB
684 composite functions in user space in the same way GadgetFS
685 lets one create USB gadgets in user space. This allows creation
686 of composite gadgets such that some of the functions are
687 implemented in kernel space (for instance Ethernet, serial or
688 mass storage) and other are implemented in user space.
690 If you say "y" or "m" here you will be able what kind of
691 configurations the gadget will provide.
693 Say "y" to link the driver statically, or "m" to build
694 a dynamically linked module called "g_ffs".
696 config USB_FUNCTIONFS_ETH
697 bool "Include configuration with CDC ECM (Ethernet)"
698 depends on USB_FUNCTIONFS && NET
700 Include a configuration with CDC ECM function (Ethernet) and the
703 config USB_FUNCTIONFS_RNDIS
704 bool "Include configuration with RNDIS (Ethernet)"
705 depends on USB_FUNCTIONFS && NET
707 Include a configuration with RNDIS function (Ethernet) and the Filesystem.
709 config USB_FUNCTIONFS_GENERIC
710 bool "Include 'pure' configuration"
711 depends on USB_FUNCTIONFS
713 Include a configuration with the Function Filesystem alone with
714 no Ethernet interface.
716 config USB_FILE_STORAGE
717 tristate "File-backed Storage Gadget (DEPRECATED)"
720 The File-backed Storage Gadget acts as a USB Mass Storage
721 disk drive. As its storage repository it can use a regular
722 file or a block device (in much the same way as the "loop"
723 device driver), specified as a module parameter.
725 Say "y" to link the driver statically, or "m" to build a
726 dynamically linked module called "g_file_storage".
728 NOTE: This driver is deprecated. Its replacement is the
731 config USB_FILE_STORAGE_TEST
732 bool "File-backed Storage Gadget testing version"
733 depends on USB_FILE_STORAGE
736 Say "y" to generate the larger testing version of the
737 File-backed Storage Gadget, useful for probing the
738 behavior of USB Mass Storage hosts. Not needed for
741 config USB_MASS_STORAGE
742 tristate "Mass Storage Gadget"
745 The Mass Storage Gadget acts as a USB Mass Storage disk drive.
746 As its storage repository it can use a regular file or a block
747 device (in much the same way as the "loop" device driver),
748 specified as a module parameter or sysfs option.
750 This driver is an updated replacement for the deprecated
751 File-backed Storage Gadget (g_file_storage).
753 Say "y" to link the driver statically, or "m" to build
754 a dynamically linked module called "g_mass_storage".
756 config USB_GADGET_TARGET
757 tristate "USB Gadget Target Fabric Module"
758 depends on TARGET_CORE
760 This fabric is an USB gadget. Two USB protocols are supported that is
761 BBB or BOT (Bulk Only Transport) and UAS (USB Attached SCSI). BOT is
762 advertised on alternative interface 0 (primary) and UAS is on
763 alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
764 UAS utilizes the USB 3.0 feature called streams support.
767 tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
769 The Serial Gadget talks to the Linux-USB generic serial driver.
770 This driver supports a CDC-ACM module option, which can be used
771 to interoperate with MS-Windows hosts or with the Linux-USB
774 This driver also supports a CDC-OBEX option. You will need a
775 user space OBEX server talking to /dev/ttyGS*, since the kernel
776 itself doesn't implement the OBEX protocol.
778 Say "y" to link the driver statically, or "m" to build a
779 dynamically linked module called "g_serial".
781 For more information, see Documentation/usb/gadget_serial.txt
782 which includes instructions and a "driver info file" needed to
783 make MS-Windows work with CDC ACM.
785 config USB_MIDI_GADGET
786 tristate "MIDI Gadget (EXPERIMENTAL)"
787 depends on SND && EXPERIMENTAL
790 The MIDI Gadget acts as a USB Audio device, with one MIDI
791 input and one MIDI output. These MIDI jacks appear as
792 a sound "card" in the ALSA sound system. Other MIDI
793 connections can then be made on the gadget system, using
794 ALSA's aconnect utility etc.
796 Say "y" to link the driver statically, or "m" to build a
797 dynamically linked module called "g_midi".
800 tristate "Printer Gadget"
802 The Printer Gadget channels data between the USB host and a
803 userspace program driving the print engine. The user space
804 program reads and writes the device file /dev/g_printer to
805 receive or send printer data. It can use ioctl calls to
806 the device file to get or set printer status.
808 Say "y" to link the driver statically, or "m" to build a
809 dynamically linked module called "g_printer".
811 For more information, see Documentation/usb/gadget_printer.txt
812 which includes sample code for accessing the device file.
814 config USB_CDC_COMPOSITE
815 tristate "CDC Composite Device (Ethernet and ACM)"
818 This driver provides two functions in one configuration:
819 a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
821 This driver requires four bulk and two interrupt endpoints,
822 plus the ability to handle altsettings. Not all peripheral
823 controllers are that capable.
825 Say "y" to link the driver statically, or "m" to build a
826 dynamically linked module.
829 tristate "Nokia composite gadget"
832 The Nokia composite gadget provides support for acm, obex
833 and phonet in only one composite gadget driver.
835 It's only really useful for N900 hardware. If you're building
836 a kernel for N900, say Y or M here. If unsure, say N.
839 tristate "CDC Composite Device (ACM and mass storage)"
842 This driver provides two functions in one configuration:
843 a mass storage, and a CDC ACM (serial port) link.
845 Say "y" to link the driver statically, or "m" to build a
846 dynamically linked module called "g_acm_ms".
849 tristate "Multifunction Composite Gadget (EXPERIMENTAL)"
850 depends on BLOCK && NET
851 select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
853 The Multifunction Composite Gadget provides Ethernet (RNDIS
854 and/or CDC Ethernet), mass storage and ACM serial link
857 You will be asked to choose which of the two configurations is
858 to be available in the gadget. At least one configuration must
859 be chosen to make the gadget usable. Selecting more than one
860 configuration will prevent Windows from automatically detecting
861 the gadget as a composite gadget, so an INF file will be needed to
864 Say "y" to link the driver statically, or "m" to build a
865 dynamically linked module called "g_multi".
867 config USB_G_MULTI_RNDIS
868 bool "RNDIS + CDC Serial + Storage configuration"
869 depends on USB_G_MULTI
872 This option enables a configuration with RNDIS, CDC Serial and
873 Mass Storage functions available in the Multifunction Composite
874 Gadget. This is the configuration dedicated for Windows since RNDIS
875 is Microsoft's protocol.
879 config USB_G_MULTI_CDC
880 bool "CDC Ethernet + CDC Serial + Storage configuration"
881 depends on USB_G_MULTI
884 This option enables a configuration with CDC Ethernet (ECM), CDC
885 Serial and Mass Storage functions available in the Multifunction
891 tristate "HID Gadget"
893 The HID gadget driver provides generic emulation of USB
894 Human Interface Devices (HID).
896 For more information, see Documentation/usb/gadget_hid.txt which
897 includes sample code for accessing the device files.
899 Say "y" to link the driver statically, or "m" to build a
900 dynamically linked module called "g_hid".
903 tristate "EHCI Debug Device Gadget"
905 This gadget emulates an EHCI Debug device. This is useful when you want
906 to interact with an EHCI Debug Port.
908 Say "y" to link the driver statically, or "m" to build a
909 dynamically linked module called "g_dbgp".
913 prompt "EHCI Debug Device mode"
914 default USB_G_DBGP_SERIAL
916 config USB_G_DBGP_PRINTK
917 depends on USB_G_DBGP
920 Directly printk() received data. No interaction.
922 config USB_G_DBGP_SERIAL
923 depends on USB_G_DBGP
926 Userland can interact using /dev/ttyGSxxx.
930 # put drivers that need isochronous transfer support (for audio
931 # or video class gadget drivers), or specific hardware, here.
933 tristate "USB Webcam Gadget"
936 The Webcam Gadget acts as a composite USB Audio and Video Class
937 device. It provides a userspace API to process UVC control requests
938 and stream video data to the host.
940 Say "y" to link the driver statically, or "m" to build a
941 dynamically linked module called "g_webcam".