Lines Matching +full:usb +full:- +full:a
1 # SPDX-License-Identifier: GPL-2.0
3 # USB Gadget support on a system involves
4 # (a) a peripheral controller, and
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
18 tristate "USB Gadget Support"
22 USB is a host/device protocol, organized with one host (such as a
24 The USB hardware is asymmetric, which makes it easier to set up:
25 you can't connect a "to-the-host" connector to a peripheral.
28 you need a low level bus controller driver, and some software
30 or are integrated with the CPU in a microcontroller. The more
36 a USB peripheral device. Configure one hardware driver for your
37 peripheral/device side bus controller, and a "gadget driver" for
44 For more information, see <http://www.linux-usb.org/gadget> and
57 debugging such a driver. Many drivers will emit so many
60 trying to track down. Never enable these messages for a
71 debugging such a driver. Many drivers will emit so many
74 trying to track down. Never enable these messages for a
83 (for a peripheral controller). The information in these
84 files may help when you're troubleshooting or bringing up a
85 driver on a new board. Enable these files by choosing "Y"
95 troubleshooting or bringing up a driver on a new board.
100 int "Maximum VBUS Power usage (2-500 mA)"
104 Some devices need to draw power from USB when they are
109 Enter the maximum power your device draws through USB, in
110 milliAmperes. The permitted range of values is 2 - 500 mA;
113 This value will be used except for system-specific gadget
121 Usually 2 buffers are enough to establish a good buffering
123 for a bursty VFS behaviour. For instance there may be CPU wake up
124 latencies that makes the VFS to appear bursty in a system with
125 an CPU on-demand governor. Especially if DMA is doing IO to
129 a module parameter as well.
136 It supports the serial gadget can be used as a console.
138 source "drivers/usb/gadget/udc/Kconfig"
141 # USB Gadget Drivers
225 # this first set of drivers all depend on bulk-capable hardware.
228 tristate "USB Gadget functions configurable through configfs"
231 A Linux USB "gadget" can be set up through configfs.
232 If this is the case, the USB functions (which from the host's
237 For more information see Documentation/usb/gadget_configfs.rst.
254 The function talks to the Linux-USB generic serial driver.
264 MS-Windows hosts or with the Linux-USB "cdc-acm" driver.
273 You will need a user space OBEX server talking to /dev/ttyGS*,
285 grouping of several ethernet frames into one USB transfer and
297 favor of simpler vendor-specific hardware, but is widely
308 a simple CDC subset is used, placing fewer demands on USB.
321 To make MS-Windows work with this, use Documentation/usb/linux.inf
322 as the "driver info file". For versions of MS-Windows older than
323 XP, you'll need to download drivers from Microsoft's website; a URL
334 CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
337 the network interface to the target (e.g. a USB cable modem), and the
339 ethernet over USB. For Linux gadgets, however, the interface with
340 the host is the same (a usbX device), so the differences are minimal.
350 The Phonet protocol implementation for USB device.
358 The Mass Storage Gadget acts as a USB Mass Storage disk drive.
359 As its storage repository it can use a regular file or a block
361 specified as a module parameter or sysfs option.
368 Loopback function loops back a configurable number of transfers.
372 USB peripheral controller driver. Then you can use host-side
374 and its driver through a basic set of functional tests.
381 The Function Filesystem (FunctionFS) lets one create USB
383 lets one create USB gadgets in user space. This allows creation
394 USB gadget Accessory support
403 USB gadget Audio Source support
415 1 AudioStreaming Interface each for USB-OUT and USB-IN.
417 on the device - the audio streams are simply sinked to and
418 sourced from a virtual ALSA sound card created. The user-space
420 received from the USB Host and choose to provide whatever it
421 wants as audio data to the USB Host.
432 1 AudioStreaming Interface each for USB-OUT and USB-IN.
433 This is a legacy driver and requires a real Audio codec
445 This Audio function is compatible with USB Audio Class
447 1 AudioStreaming Interface each for USB-OUT and USB-IN.
449 on the device - the audio streams are simply sinked to and
450 sourced from a virtual ALSA sound card created. The user-space
452 received from the USB Host and choose to provide whatever it
453 wants as audio data to the USB Host.
463 The MIDI Function acts as a USB Audio device, with one MIDI
465 a sound "card" in the ALSA sound system. Other MIDI
474 The HID function driver provides generic emulation of USB
477 For more information, see Documentation/usb/gadget_hid.rst.
480 bool "USB Webcam function"
487 The Webcam function acts as a composite USB Audio and Video Class
488 device. It provides a userspace API to process UVC control requests
496 The Printer function channels data between the USB host and a
502 For more information, see Documentation/usb/gadget_printer.rst
506 bool "USB Gadget Target Fabric"
512 This fabric is a USB gadget component. Two USB protocols are
514 (USB Attached SCSI). BOT is advertised on alternative
517 UAS utilizes the USB 3.0 feature called streams support.
519 source "drivers/usb/gadget/legacy/Kconfig"