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"
19 USB is a master/slave protocol, organized with one master
20 host (such as a PC) controlling up to 127 peripheral devices.
21 The USB hardware is asymmetric, which makes it easier to set up:
22 you can't connect a "to-the-host" connector to a peripheral.
24 Linux can run in the host, or in the peripheral. In both cases
25 you need a low level bus controller driver, and some software
26 talking to it. Peripheral controllers are often discrete silicon,
27 or are integrated with the CPU in a microcontroller. The more
28 familiar host side controllers have names like "EHCI", "OHCI",
29 or "UHCI", and are usually integrated into southbridges on PC
32 Enable this configuration option if you want to run Linux inside
33 a USB peripheral device. Configure one hardware driver for your
34 peripheral/device side bus controller, and a "gadget driver" for
35 your peripheral protocol. (If you use modular gadget drivers,
36 you may configure more than one.)
38 If in doubt, say "N" and don't enable these drivers; most people
39 don't have this kind of hardware (except maybe inside Linux PDAs).
41 For more information, see <http://www.linux-usb.org/gadget> and
42 the kernel DocBook documentation for this API.
46 config USB_GADGET_DEBUG
47 boolean "Debugging messages (DEVELOPMENT)"
48 depends on DEBUG_KERNEL
50 Many controller and gadget drivers will print some debugging
51 messages if you use this option to ask for those messages.
53 Avoid enabling these messages, even if you're actively
54 debugging such a driver. Many drivers will emit so many
55 messages that the driver timings are affected, which will
56 either create new failure modes or remove the one you're
57 trying to track down. Never enable these messages for a
60 config USB_GADGET_DEBUG_FILES
61 boolean "Debugging information files (DEVELOPMENT)"
64 Some of the drivers in the "gadget" framework can expose
65 debugging information in files such as /proc/driver/udc
66 (for a peripheral controller). The information in these
67 files may help when you're troubleshooting or bringing up a
68 driver on a new board. Enable these files by choosing "Y"
69 here. If in doubt, or to conserve kernel memory, say "N".
71 config USB_GADGET_DEBUG_FS
72 boolean "Debugging information files in debugfs (DEVELOPMENT)"
75 Some of the drivers in the "gadget" framework can expose
76 debugging information in files under /sys/kernel/debug/.
77 The information in these files may help when you're
78 troubleshooting or bringing up a driver on a new board.
79 Enable these files by choosing "Y" here. If in doubt, or
80 to conserve kernel memory, say "N".
82 config USB_GADGET_VBUS_DRAW
83 int "Maximum VBUS Power usage (2-500 mA)"
87 Some devices need to draw power from USB when they are
88 configured, perhaps to operate circuitry or to recharge
89 batteries. This is in addition to any local power supply,
90 such as an AC adapter or batteries.
92 Enter the maximum power your device draws through USB, in
93 milliAmperes. The permitted range of values is 2 - 500 mA;
94 0 mA would be legal, but can make some hosts misbehave.
96 This value will be used except for system-specific gadget
97 drivers that have more specific information.
100 # USB Peripheral Controller Support
102 # The order here is alphabetical, except that integrated controllers go
103 # before discrete ones so they will be the initial/default value:
104 # - integrated/SOC controllers first
105 # - licensed IP used in both SOC and discrete versions
106 # - discrete ones (including all PCI-only controllers)
107 # - debug/dummy gadget+hcd is last.
110 prompt "USB Peripheral Controller"
111 depends on USB_GADGET
113 A USB device uses a controller to talk to its host.
114 Systems should have only one such upstream link.
115 Many controller drivers are platform-specific; these
116 often need board-specific hooks.
119 # Integrated controllers
123 tristate "Atmel AT91 USB Device Port"
124 depends on ARCH_AT91 && !ARCH_AT91SAM9RL && !ARCH_AT91CAP9 && !ARCH_AT91SAM9G45
126 Many Atmel AT91 processors (such as the AT91RM2000) have a
127 full speed USB Device Port with support for five configurable
128 endpoints (plus endpoint zero).
130 Say "y" to link the driver statically, or "m" to build a
131 dynamically linked module called "at91_udc" and force all
132 gadget drivers to also be dynamically linked.
134 config USB_ATMEL_USBA
135 tristate "Atmel USBA"
136 select USB_GADGET_DUALSPEED
137 depends on AVR32 || ARCH_AT91CAP9 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
139 USBA is the integrated high-speed USB Device controller on
140 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
143 tristate "Freescale Highspeed USB DR Peripheral Controller"
144 depends on FSL_SOC || ARCH_MXC
145 select USB_GADGET_DUALSPEED
146 select USB_FSL_MPH_DR_OF if OF
148 Some of Freescale PowerPC processors have a High Speed
149 Dual-Role(DR) USB controller, which supports device mode.
151 The number of programmable endpoints is different through
154 Say "y" to link the driver statically, or "m" to build a
155 dynamically linked module called "fsl_usb2_udc" and force
156 all gadget drivers to also be dynamically linked.
159 tristate "Faraday FUSB300 USB Peripheral Controller"
160 depends on !PHYS_ADDR_T_64BIT
161 select USB_GADGET_DUALSPEED
163 Faraday usb device controller FUSB300 driver
166 tristate "OMAP USB Device Controller"
168 select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
169 select USB_OTG_UTILS if ARCH_OMAP
171 Many Texas Instruments OMAP processors have flexible full
172 speed USB device controllers, with support for up to 30
173 endpoints (plus endpoint zero). This driver supports the
174 controller in the OMAP 1611, and should work with controllers
175 in other OMAP processors too, given minor tweaks.
177 Say "y" to link the driver statically, or "m" to build a
178 dynamically linked module called "omap_udc" and force all
179 gadget drivers to also be dynamically linked.
182 tristate "PXA 25x or IXP 4xx"
183 depends on (ARCH_PXA && PXA25x) || ARCH_IXP4XX
186 Intel's PXA 25x series XScale ARM-5TE processors include
187 an integrated full speed USB 1.1 device controller. The
188 controller in the IXP 4xx series is register-compatible.
190 It has fifteen fixed-function endpoints, as well as endpoint
191 zero (for control transfers).
193 Say "y" to link the driver statically, or "m" to build a
194 dynamically linked module called "pxa25x_udc" and force all
195 gadget drivers to also be dynamically linked.
197 # if there's only one gadget driver, using only two bulk endpoints,
198 # don't waste memory for the other endpoints
199 config USB_PXA25X_SMALL
200 depends on USB_PXA25X
202 default n if USB_ETH_RNDIS
203 default y if USB_ZERO
205 default y if USB_G_SERIAL
208 tristate "Renesas R8A66597 USB Peripheral Controller"
209 select USB_GADGET_DUALSPEED
211 R8A66597 is a discrete USB host and peripheral controller chip that
212 supports both full and high speed USB 2.0 data transfers.
213 It has nine configurable endpoints, and endpoint zero.
215 Say "y" to link the driver statically, or "m" to build a
216 dynamically linked module called "r8a66597_udc" and force all
217 gadget drivers to also be dynamically linked.
219 config USB_RENESAS_USBHS_UDC
220 tristate 'Renesas USBHS controller'
221 depends on SUPERH || ARCH_SHMOBILE
222 depends on USB_RENESAS_USBHS
223 select USB_GADGET_DUALSPEED
225 Renesas USBHS is a discrete USB host and peripheral controller chip
226 that supports both full and high speed USB 2.0 data transfers.
227 It has nine or more configurable endpoints, and endpoint zero.
229 Say "y" to link the driver statically, or "m" to build a
230 dynamically linked module called "renesas_usbhs" and force all
231 gadget drivers to also be dynamically linked.
235 depends on ARCH_PXA && (PXA27x || PXA3xx)
238 Intel's PXA 27x series XScale ARM v5TE processors include
239 an integrated full speed USB 1.1 device controller.
241 It has up to 23 endpoints, as well as endpoint zero (for
244 Say "y" to link the driver statically, or "m" to build a
245 dynamically linked module called "pxa27x_udc" and force all
246 gadget drivers to also be dynamically linked.
249 tristate "S3C HS/OtG USB Device controller"
250 depends on S3C_DEV_USB_HSOTG
251 select USB_GADGET_S3C_HSOTG_PIO
252 select USB_GADGET_DUALSPEED
254 The Samsung S3C64XX USB2.0 high-speed gadget controller
255 integrated into the S3C64XX series SoC.
258 tristate "Freescale IMX USB Peripheral Controller"
261 Freescale's IMX series include an integrated full speed
262 USB 1.1 device controller. The controller in the IMX series
263 is register-compatible.
265 It has Six fixed-function endpoints, as well as endpoint
266 zero (for control transfers).
268 Say "y" to link the driver statically, or "m" to build a
269 dynamically linked module called "imx_udc" and force all
270 gadget drivers to also be dynamically linked.
273 tristate "S3C2410 USB Device Controller"
274 depends on ARCH_S3C2410
276 Samsung's S3C2410 is an ARM-4 processor with an integrated
277 full speed USB 1.1 device controller. It has 4 configurable
278 endpoints, as well as endpoint zero (for control transfers).
280 This driver has been tested on the S3C2410, S3C2412, and
283 config USB_S3C2410_DEBUG
284 boolean "S3C2410 udc debug messages"
285 depends on USB_S3C2410
288 tristate "S3C2416, S3C2443 and S3C2450 USB Device Controller"
289 depends on ARCH_S3C2410
290 select USB_GADGET_DUALSPEED
292 Samsung's S3C2416, S3C2443 and S3C2450 is an ARM9 based SoC
293 integrated with dual speed USB 2.0 device controller. It has
294 8 endpoints, as well as endpoint zero.
296 This driver has been tested on S3C2416 and S3C2450 processors.
299 tristate "PXA9xx Processor USB2.0 controller"
301 select USB_GADGET_DUALSPEED
303 PXA9xx Processor series include a high speed USB2.0 device
304 controller, which support high speed and full speed USB peripheral.
306 config USB_GADGET_DWC3
307 tristate "DesignWare USB3.0 (DRD) Controller"
309 select USB_GADGET_DUALSPEED
310 select USB_GADGET_SUPERSPEED
312 DesignWare USB3.0 controller is a SuperSpeed USB3.0 Controller
313 which can be configured for peripheral-only, host-only, hub-only
314 and Dual-Role operation. This Controller was first integrated into
315 the OMAP5 series of processors. More information about the OMAP5
316 version of this controller, refer to http://www.ti.com/omap5.
319 # Controllers available in both integrated and discrete versions
322 # musb builds in ../musb along with host support
323 config USB_GADGET_MUSB_HDRC
324 tristate "Inventra HDRC USB Peripheral (TI, ADI, ...)"
325 depends on USB_MUSB_HDRC
326 select USB_GADGET_DUALSPEED
328 This OTG-capable silicon IP is used in dual designs including
329 the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin
332 tristate "Renesas M66592 USB Peripheral Controller"
333 select USB_GADGET_DUALSPEED
335 M66592 is a discrete USB peripheral controller chip that
336 supports both full and high speed USB 2.0 data transfers.
337 It has seven configurable endpoints, and endpoint zero.
339 Say "y" to link the driver statically, or "m" to build a
340 dynamically linked module called "m66592_udc" and force all
341 gadget drivers to also be dynamically linked.
344 # Controllers available only in discrete form (and all PCI controllers)
347 config USB_AMD5536UDC
348 tristate "AMD5536 UDC"
350 select USB_GADGET_DUALSPEED
352 The AMD5536 UDC is part of the AMD Geode CS5536, an x86 southbridge.
353 It is a USB Highspeed DMA capable USB device controller. Beside ep0
354 it provides 4 IN and 4 OUT endpoints (bulk or interrupt type).
355 The UDC port supports OTG operation, and may be used as a host port
356 if it's not being used to implement peripheral or OTG roles.
358 Say "y" to link the driver statically, or "m" to build a
359 dynamically linked module called "amd5536udc" and force all
360 gadget drivers to also be dynamically linked.
363 tristate "Freescale QE/CPM USB Device Controller"
364 depends on FSL_SOC && (QUICC_ENGINE || CPM)
366 Some of Freescale PowerPC processors have a Full Speed
367 QE/CPM2 USB controller, which support device mode with 4
368 programmable endpoints. This driver supports the
369 controller in the MPC8360 and MPC8272, and should work with
370 controllers having QE or CPM2, given minor tweaks.
372 Set CONFIG_USB_GADGET to "m" to build this driver as a
373 dynamically linked module called "fsl_qe_udc".
375 config USB_CI13XXX_PCI
376 tristate "MIPS USB CI13xxx PCI UDC"
378 select USB_GADGET_DUALSPEED
380 MIPS USB IP core family device controller
381 Currently it only supports IP part number CI13412
383 Say "y" to link the driver statically, or "m" to build a
384 dynamically linked module called "ci13xxx_udc" and force all
385 gadget drivers to also be dynamically linked.
388 tristate "PLX NET2272"
389 select USB_GADGET_DUALSPEED
391 PLX NET2272 is a USB peripheral controller which supports
392 both full and high speed USB 2.0 data transfers.
394 It has three configurable endpoints, as well as endpoint zero
395 (for control transfer).
396 Say "y" to link the driver statically, or "m" to build a
397 dynamically linked module called "net2272" and force all
398 gadget drivers to also be dynamically linked.
400 config USB_NET2272_DMA
401 boolean "Support external DMA controller"
402 depends on USB_NET2272
404 The NET2272 part can optionally support an external DMA
405 controller, but your board has to have support in the
408 If unsure, say "N" here. The driver works fine in PIO mode.
411 tristate "NetChip 228x"
413 select USB_GADGET_DUALSPEED
415 NetChip 2280 / 2282 is a PCI based USB peripheral controller which
416 supports both full and high speed USB 2.0 data transfers.
418 It has six configurable endpoints, as well as endpoint zero
419 (for control transfers) and several endpoints with dedicated
422 Say "y" to link the driver statically, or "m" to build a
423 dynamically linked module called "net2280" and force all
424 gadget drivers to also be dynamically linked.
427 tristate "Toshiba TC86C001 'Goku-S'"
430 The Toshiba TC86C001 is a PCI device which includes controllers
431 for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).
433 The device controller has three configurable (bulk or interrupt)
434 endpoints, plus endpoint zero (for control transfers).
436 Say "y" to link the driver statically, or "m" to build a
437 dynamically linked module called "goku_udc" and to force all
438 gadget drivers to also be dynamically linked.
441 tristate "Intel Langwell USB Device Controller"
443 depends on !PHYS_ADDR_T_64BIT
444 select USB_GADGET_DUALSPEED
446 Intel Langwell USB Device Controller is a High-Speed USB
447 On-The-Go device controller.
449 The number of programmable endpoints is different through
452 Say "y" to link the driver statically, or "m" to build a
453 dynamically linked module called "langwell_udc" and force all
454 gadget drivers to also be dynamically linked.
457 tristate "Intel EG20T PCH/OKI SEMICONDUCTOR ML7213 IOH UDC"
459 select USB_GADGET_DUALSPEED
461 This is a USB device driver for EG20T PCH.
462 EG20T PCH is the platform controller hub that is used in Intel's
463 general embedded platform. EG20T PCH has USB device interface.
464 Using this interface, it is able to access system devices connected
466 This driver enables USB device function.
467 USB device is a USB peripheral controller which
468 supports both full and high speed USB 2.0 data transfers.
469 This driver supports both control transfer and bulk transfer modes.
470 This driver dose not support interrupt transfer or isochronous
473 This driver also can be used for OKI SEMICONDUCTOR's ML7213 which is
474 for IVI(In-Vehicle Infotainment) use.
475 ML7213 is companion chip for Intel Atom E6xx series.
476 ML7213 is completely compatible for Intel EG20T PCH.
478 config USB_CI13XXX_MSM
479 tristate "MIPS USB CI13xxx for MSM"
481 select USB_GADGET_DUALSPEED
484 MSM SoC has chipidea USB controller. This driver uses
486 This driver depends on OTG driver for PHY initialization,
487 clock management, powering up VBUS, and power management.
488 This driver is not supported on boards like trout which
491 Say "y" to link the driver statically, or "m" to build a
492 dynamically linked module called "ci13xxx_msm" and force all
493 gadget drivers to also be dynamically linked.
496 # LAST -- dummy/emulated controller
500 tristate "Dummy HCD (DEVELOPMENT)"
501 depends on USB=y || (USB=m && USB_GADGET=m)
502 select USB_GADGET_DUALSPEED
503 select USB_GADGET_SUPERSPEED
505 This host controller driver emulates USB, looping all data transfer
506 requests back to a USB "gadget driver" in the same host. The host
507 side is the master; the gadget side is the slave. Gadget drivers
508 can be high, full, or low speed; and they have access to endpoints
509 like those from NET2280, PXA2xx, or SA1100 hardware.
511 This may help in some stages of creating a driver to embed in a
512 Linux device, since it lets you debug several parts of the gadget
513 driver without its hardware or drivers being involved.
515 Since such a gadget side driver needs to interoperate with a host
516 side Linux-USB device driver, this may help to debug both sides
517 of a USB protocol stack.
519 Say "y" to link the driver statically, or "m" to build a
520 dynamically linked module called "dummy_hcd" and force all
521 gadget drivers to also be dynamically linked.
523 # NOTE: Please keep dummy_hcd LAST so that "real hardware" appears
524 # first and will be selected by default.
528 # Selected by UDC drivers that support high-speed operation.
529 config USB_GADGET_DUALSPEED
531 depends on USB_GADGET
533 # Selected by UDC drivers that support super-speed opperation
534 config USB_GADGET_SUPERSPEED
536 depends on USB_GADGET
537 depends on USB_GADGET_DUALSPEED
543 tristate "USB Gadget Drivers"
544 depends on USB_GADGET
547 A Linux "Gadget Driver" talks to the USB Peripheral Controller
548 driver through the abstract "gadget" API. Some other operating
549 systems call these "client" drivers, of which "class drivers"
550 are a subset (implementing a USB device class specification).
551 A gadget driver implements one or more USB functions using
552 the peripheral hardware.
554 Gadget drivers are hardware-neutral, or "platform independent",
555 except that they sometimes must understand quirks or limitations
556 of the particular controllers they work with. For example, when
557 a controller doesn't support alternate configurations or provide
558 enough of the right types of endpoints, the gadget driver might
559 not be able work with that controller, or might need to implement
560 a less common variant of a device class protocol.
562 # this first set of drivers all depend on bulk-capable hardware.
565 tristate "Gadget Zero (DEVELOPMENT)"
567 Gadget Zero is a two-configuration device. It either sinks and
568 sources bulk data; or it loops back a configurable number of
569 transfers. It also implements control requests, for "chapter 9"
570 conformance. The driver needs only two bulk-capable endpoints, so
571 it can work on top of most device-side usb controllers. It's
572 useful for testing, and is also a working example showing how
573 USB "gadget drivers" can be written.
575 Make this be the first driver you try using on top of any new
576 USB peripheral controller driver. Then you can use host-side
577 test software, like the "usbtest" driver, to put your hardware
578 and its driver through a basic set of functional tests.
580 Gadget Zero also works with the host-side "usb-skeleton" driver,
581 and with many kinds of host-side test software. You may need
582 to tweak product and vendor IDs before host software knows about
583 this device, and arrange to select an appropriate configuration.
585 Say "y" to link the driver statically, or "m" to build a
586 dynamically linked module called "g_zero".
588 config USB_ZERO_HNPTEST
589 boolean "HNP Test Device"
590 depends on USB_ZERO && USB_OTG
592 You can configure this device to enumerate using the device
593 identifiers of the USB-OTG test device. That means that when
594 this gadget connects to another OTG device, with this one using
595 the "B-Peripheral" role, that device will use HNP to let this
596 one serve as the USB host instead (in the "B-Host" role).
599 tristate "Audio Gadget (EXPERIMENTAL)"
603 Gadget Audio is compatible with USB Audio Class specification 1.0.
604 It will include at least one AudioControl interface, zero or more
605 AudioStream interface and zero or more MIDIStream interface.
607 Gadget Audio will use on-board ALSA (CONFIG_SND) audio card to
608 playback or capture audio stream.
610 Say "y" to link the driver statically, or "m" to build a
611 dynamically linked module called "g_audio".
614 tristate "Ethernet Gadget (with CDC Ethernet support)"
618 This driver implements Ethernet style communication, in one of
621 - The "Communication Device Class" (CDC) Ethernet Control Model.
622 That protocol is often avoided with pure Ethernet adapters, in
623 favor of simpler vendor-specific hardware, but is widely
624 supported by firmware for smart network devices.
626 - On hardware can't implement that protocol, a simple CDC subset
627 is used, placing fewer demands on USB.
629 - CDC Ethernet Emulation Model (EEM) is a newer standard that has
630 a simpler interface that can be used by more USB hardware.
632 RNDIS support is an additional option, more demanding than than
635 Within the USB device, this gadget driver exposes a network device
636 "usbX", where X depends on what other networking devices you have.
637 Treat it like a two-node Ethernet link: host, and gadget.
639 The Linux-USB host-side "usbnet" driver interoperates with this
640 driver, so that deep I/O queues can be supported. On 2.4 kernels,
641 use "CDCEther" instead, if you're using the CDC option. That CDC
642 mode should also interoperate with standard CDC Ethernet class
643 drivers on other host operating systems.
645 Say "y" to link the driver statically, or "m" to build a
646 dynamically linked module called "g_ether".
653 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
654 and Microsoft provides redistributable binary RNDIS drivers for
655 older versions of Windows.
657 If you say "y" here, the Ethernet gadget driver will try to provide
658 a second device configuration, supporting RNDIS to talk to such
661 To make MS-Windows work with this, use Documentation/usb/linux.inf
662 as the "driver info file". For versions of MS-Windows older than
663 XP, you'll need to download drivers from Microsoft's website; a URL
664 is given in comments found in that info file.
667 bool "Ethernet Emulation Model (EEM) support"
671 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
672 and therefore can be supported by more hardware. Technically ECM and
673 EEM are designed for different applications. The ECM model extends
674 the network interface to the target (e.g. a USB cable modem), and the
675 EEM model is for mobile devices to communicate with hosts using
676 ethernet over USB. For Linux gadgets, however, the interface with
677 the host is the same (a usbX device), so the differences are minimal.
679 If you say "y" here, the Ethernet gadget driver will use the EEM
680 protocol rather than ECM. If unsure, say "n".
683 tristate "Network Control Model (NCM) support"
687 This driver implements USB CDC NCM subclass standard. NCM is
688 an advanced protocol for Ethernet encapsulation, allows grouping
689 of several ethernet frames into one USB transfer and diffferent
690 alignment possibilities.
692 Say "y" to link the driver statically, or "m" to build a
693 dynamically linked module called "g_ncm".
696 tristate "Gadget Filesystem (EXPERIMENTAL)"
697 depends on EXPERIMENTAL
699 This driver provides a filesystem based API that lets user mode
700 programs implement a single-configuration USB device, including
701 endpoint I/O and control requests that don't relate to enumeration.
702 All endpoints, transfer speeds, and transfer types supported by
703 the hardware are available, through read() and write() calls.
705 Currently, this option is still labelled as EXPERIMENTAL because
706 of existing race conditions in the underlying in-kernel AIO core.
708 Say "y" to link the driver statically, or "m" to build a
709 dynamically linked module called "gadgetfs".
711 config USB_FUNCTIONFS
712 tristate "Function Filesystem (EXPERIMENTAL)"
713 depends on EXPERIMENTAL
714 select USB_FUNCTIONFS_GENERIC if !(USB_FUNCTIONFS_ETH || USB_FUNCTIONFS_RNDIS)
716 The Function Filesystem (FunctionFS) lets one create USB
717 composite functions in user space in the same way GadgetFS
718 lets one create USB gadgets in user space. This allows creation
719 of composite gadgets such that some of the functions are
720 implemented in kernel space (for instance Ethernet, serial or
721 mass storage) and other are implemented in user space.
723 If you say "y" or "m" here you will be able what kind of
724 configurations the gadget will provide.
726 Say "y" to link the driver statically, or "m" to build
727 a dynamically linked module called "g_ffs".
729 config USB_FUNCTIONFS_ETH
730 bool "Include configuration with CDC ECM (Ethernet)"
731 depends on USB_FUNCTIONFS && NET
733 Include a configuration with CDC ECM function (Ethernet) and the
736 config USB_FUNCTIONFS_RNDIS
737 bool "Include configuration with RNDIS (Ethernet)"
738 depends on USB_FUNCTIONFS && NET
740 Include a configuration with RNDIS function (Ethernet) and the Filesystem.
742 config USB_FUNCTIONFS_GENERIC
743 bool "Include 'pure' configuration"
744 depends on USB_FUNCTIONFS
746 Include a configuration with the Function Filesystem alone with
747 no Ethernet interface.
749 config USB_FILE_STORAGE
750 tristate "File-backed Storage Gadget (DEPRECATED)"
753 The File-backed Storage Gadget acts as a USB Mass Storage
754 disk drive. As its storage repository it can use a regular
755 file or a block device (in much the same way as the "loop"
756 device driver), specified as a module parameter.
758 Say "y" to link the driver statically, or "m" to build a
759 dynamically linked module called "g_file_storage".
761 NOTE: This driver is deprecated. Its replacement is the
764 config USB_FILE_STORAGE_TEST
765 bool "File-backed Storage Gadget testing version"
766 depends on USB_FILE_STORAGE
769 Say "y" to generate the larger testing version of the
770 File-backed Storage Gadget, useful for probing the
771 behavior of USB Mass Storage hosts. Not needed for
774 config USB_MASS_STORAGE
775 tristate "Mass Storage Gadget"
778 The Mass Storage Gadget acts as a USB Mass Storage disk drive.
779 As its storage repository it can use a regular file or a block
780 device (in much the same way as the "loop" device driver),
781 specified as a module parameter or sysfs option.
783 This driver is an updated replacement for the deprecated
784 File-backed Storage Gadget (g_file_storage).
786 Say "y" to link the driver statically, or "m" to build
787 a dynamically linked module called "g_mass_storage".
790 tristate "Serial Gadget (with CDC ACM and CDC OBEX support)"
792 The Serial Gadget talks to the Linux-USB generic serial driver.
793 This driver supports a CDC-ACM module option, which can be used
794 to interoperate with MS-Windows hosts or with the Linux-USB
797 This driver also supports a CDC-OBEX option. You will need a
798 user space OBEX server talking to /dev/ttyGS*, since the kernel
799 itself doesn't implement the OBEX protocol.
801 Say "y" to link the driver statically, or "m" to build a
802 dynamically linked module called "g_serial".
804 For more information, see Documentation/usb/gadget_serial.txt
805 which includes instructions and a "driver info file" needed to
806 make MS-Windows work with CDC ACM.
808 config USB_MIDI_GADGET
809 tristate "MIDI Gadget (EXPERIMENTAL)"
810 depends on SND && EXPERIMENTAL
813 The MIDI Gadget acts as a USB Audio device, with one MIDI
814 input and one MIDI output. These MIDI jacks appear as
815 a sound "card" in the ALSA sound system. Other MIDI
816 connections can then be made on the gadget system, using
817 ALSA's aconnect utility etc.
819 Say "y" to link the driver statically, or "m" to build a
820 dynamically linked module called "g_midi".
823 tristate "Printer Gadget"
825 The Printer Gadget channels data between the USB host and a
826 userspace program driving the print engine. The user space
827 program reads and writes the device file /dev/g_printer to
828 receive or send printer data. It can use ioctl calls to
829 the device file to get or set printer status.
831 Say "y" to link the driver statically, or "m" to build a
832 dynamically linked module called "g_printer".
834 For more information, see Documentation/usb/gadget_printer.txt
835 which includes sample code for accessing the device file.
837 config USB_CDC_COMPOSITE
838 tristate "CDC Composite Device (Ethernet and ACM)"
841 This driver provides two functions in one configuration:
842 a CDC Ethernet (ECM) link, and a CDC ACM (serial port) link.
844 This driver requires four bulk and two interrupt endpoints,
845 plus the ability to handle altsettings. Not all peripheral
846 controllers are that capable.
848 Say "y" to link the driver statically, or "m" to build a
849 dynamically linked module.
852 tristate "Nokia composite gadget"
855 The Nokia composite gadget provides support for acm, obex
856 and phonet in only one composite gadget driver.
858 It's only really useful for N900 hardware. If you're building
859 a kernel for N900, say Y or M here. If unsure, say N.
862 tristate "Multifunction Composite Gadget (EXPERIMENTAL)"
863 depends on BLOCK && NET
864 select USB_G_MULTI_CDC if !USB_G_MULTI_RNDIS
866 The Multifunction Composite Gadget provides Ethernet (RNDIS
867 and/or CDC Ethernet), mass storage and ACM serial link
870 You will be asked to choose which of the two configurations is
871 to be available in the gadget. At least one configuration must
872 be chosen to make the gadget usable. Selecting more than one
873 configuration will prevent Windows from automatically detecting
874 the gadget as a composite gadget, so an INF file will be needed to
877 Say "y" to link the driver statically, or "m" to build a
878 dynamically linked module called "g_multi".
880 config USB_G_MULTI_RNDIS
881 bool "RNDIS + CDC Serial + Storage configuration"
882 depends on USB_G_MULTI
885 This option enables a configuration with RNDIS, CDC Serial and
886 Mass Storage functions available in the Multifunction Composite
887 Gadget. This is the configuration dedicated for Windows since RNDIS
888 is Microsoft's protocol.
892 config USB_G_MULTI_CDC
893 bool "CDC Ethernet + CDC Serial + Storage configuration"
894 depends on USB_G_MULTI
897 This option enables a configuration with CDC Ethernet (ECM), CDC
898 Serial and Mass Storage functions available in the Multifunction
904 tristate "HID Gadget"
906 The HID gadget driver provides generic emulation of USB
907 Human Interface Devices (HID).
909 For more information, see Documentation/usb/gadget_hid.txt which
910 includes sample code for accessing the device files.
912 Say "y" to link the driver statically, or "m" to build a
913 dynamically linked module called "g_hid".
916 tristate "EHCI Debug Device Gadget"
918 This gadget emulates an EHCI Debug device. This is useful when you want
919 to interact with an EHCI Debug Port.
921 Say "y" to link the driver statically, or "m" to build a
922 dynamically linked module called "g_dbgp".
926 prompt "EHCI Debug Device mode"
927 default USB_G_DBGP_SERIAL
929 config USB_G_DBGP_PRINTK
930 depends on USB_G_DBGP
933 Directly printk() received data. No interaction.
935 config USB_G_DBGP_SERIAL
936 depends on USB_G_DBGP
939 Userland can interact using /dev/ttyGSxxx.
943 # put drivers that need isochronous transfer support (for audio
944 # or video class gadget drivers), or specific hardware, here.
946 tristate "USB Webcam Gadget"
949 The Webcam Gadget acts as a composite USB Audio and Video Class
950 device. It provides a userspace API to process UVC control requests
951 and stream video data to the host.
953 Say "y" to link the driver statically, or "m" to build a
954 dynamically linked module called "g_webcam".