Lines Matching +full:many +full:- +full:to +full:- +full:one
1 # SPDX-License-Identifier: GPL-2.0
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).
22 USB is a host/device protocol, organized with one host (such as a
23 PC) controlling up to 127 peripheral devices.
24 The USB hardware is asymmetric, which makes it easier to set up:
25 you can't connect a "to-the-host" connector to a peripheral.
29 talking to it. Peripheral controllers are often discrete silicon,
35 Enable this configuration option if you want to run Linux inside
36 a USB peripheral device. Configure one hardware driver for your
39 you may configure more than one.)
44 For more information, see <http://www.linux-usb.org/gadget> and
53 Many controller and gadget drivers will print some debugging
54 messages if you use this option to ask for those messages.
57 debugging such a driver. Many drivers will emit so many
59 either create new failure modes or remove the one you're
60 trying to track down. Never enable these messages for a
67 Many controller and gadget drivers will print verbose debugging
68 messages if you use this option to ask for those messages.
71 debugging such a driver. Many drivers will emit so many
73 either create new failure modes or remove the one you're
74 trying to track down. Never enable these messages for a
86 here. If in doubt, or to conserve kernel memory, say "N".
97 to conserve kernel memory, say "N".
100 int "Maximum VBUS Power usage (2-500 mA)"
104 Some devices need to draw power from USB when they are
105 configured, perhaps to operate circuitry or to recharge
106 batteries. This is in addition to any local power supply,
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
122 pipeline. The number may be increased in order to compensate
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
127 save often and spin up occasionally to move data within VFS.
224 # this first set of drivers all depend on bulk-capable hardware.
245 The function talks to the Linux-USB generic serial driver.
254 ACM serial link. This function can be used to interoperate with
255 MS-Windows hosts or with the Linux-USB "cdc-acm" driver.
264 You will need a user space OBEX server talking to /dev/ttyGS*,
276 grouping of several ethernet frames into one USB transfer and
288 favor of simpler vendor-specific hardware, but is widely
312 To make MS-Windows work with this, use Documentation/usb/linux.inf
313 as the "driver info file". For versions of MS-Windows older than
314 XP, you'll need to download drivers from Microsoft's website; a URL
328 the network interface to the target (e.g. a USB cable modem), and the
329 EEM model is for mobile devices to communicate with hosts using
363 USB peripheral controller driver. Then you can use host-side
364 test software, like the "usbtest" driver, to put your hardware
372 The Function Filesystem (FunctionFS) lets one create USB
374 lets one create USB gadgets in user space. This allows creation
389 1 AudioStreaming Interface each for USB-OUT and USB-IN.
390 This driver doesn't expect any real Audio codec to be present
391 on the device - the audio streams are simply sinked to and
392 sourced from a virtual ALSA sound card created. The user-space
393 application may choose to do whatever it wants with the data
394 received from the USB Host and choose to provide whatever it
395 wants as audio data to the USB Host.
406 1 AudioStreaming Interface each for USB-OUT and USB-IN.
408 to be present on the device.
421 1 AudioStreaming Interface each for USB-OUT and USB-IN.
422 This driver doesn't expect any real Audio codec to be present
423 on the device - the audio streams are simply sinked to and
424 sourced from a virtual ALSA sound card created. The user-space
425 application may choose to do whatever it wants with the data
426 received from the USB Host and choose to provide whatever it
427 wants as audio data to the USB Host.
437 The MIDI Function acts as a USB Audio device, with one MIDI
438 input and one MIDI output. These MIDI jacks appear as
453 USB MIDI 2.0 interface, looped back to ALSA UMP rawmidi
478 device. It provides a userspace API to process UVC control requests
479 and stream video data to the host.
488 program reads and writes the device file /dev/g_printer<X> to
489 receive or send printer data. It can use ioctl calls to
490 the device file to get or set printer status.