2019-01-17 01:23:50 -07:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2005-04-16 15:20:36 -07:00
|
|
|
#
|
|
|
|
|
# USB Gadget support on a system involves
|
|
|
|
|
# (a) a peripheral controller, and
|
|
|
|
|
# (b) the gadget driver using it.
|
|
|
|
|
#
|
|
|
|
|
# NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
|
|
|
|
|
#
|
|
|
|
|
# - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
|
|
|
|
|
# - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
|
2006-10-03 13:36:44 -07:00
|
|
|
# - Some systems have both kinds of controllers.
|
2005-04-16 15:20:36 -07:00
|
|
|
#
|
|
|
|
|
# With help from a special transceiver and a "Mini-AB" jack, systems with
|
|
|
|
|
# both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
|
|
|
|
|
#
|
|
|
|
|
|
2008-01-24 01:36:31 -07:00
|
|
|
menuconfig USB_GADGET
|
|
|
|
|
tristate "USB Gadget Support"
|
2016-03-23 09:45:08 -07:00
|
|
|
select USB_COMMON
|
2011-11-17 14:42:24 -07:00
|
|
|
select NLS
|
2005-04-16 15:20:36 -07:00
|
|
|
help
|
2020-06-30 10:41:23 -07:00
|
|
|
USB is a host/device protocol, organized with one host (such as a
|
|
|
|
|
PC) controlling up to 127 peripheral devices.
|
2005-04-16 15:20:36 -07:00
|
|
|
The USB hardware is asymmetric, which makes it easier to set up:
|
|
|
|
|
you can't connect a "to-the-host" connector to a peripheral.
|
|
|
|
|
|
|
|
|
|
Linux can run in the host, or in the peripheral. In both cases
|
|
|
|
|
you need a low level bus controller driver, and some software
|
|
|
|
|
talking to it. Peripheral controllers are often discrete silicon,
|
|
|
|
|
or are integrated with the CPU in a microcontroller. The more
|
2006-08-22 13:40:15 -07:00
|
|
|
familiar host side controllers have names like "EHCI", "OHCI",
|
2005-04-16 15:20:36 -07:00
|
|
|
or "UHCI", and are usually integrated into southbridges on PC
|
|
|
|
|
motherboards.
|
|
|
|
|
|
|
|
|
|
Enable this configuration option if you want to run Linux inside
|
|
|
|
|
a USB peripheral device. Configure one hardware driver for your
|
|
|
|
|
peripheral/device side bus controller, and a "gadget driver" for
|
|
|
|
|
your peripheral protocol. (If you use modular gadget drivers,
|
|
|
|
|
you may configure more than one.)
|
|
|
|
|
|
|
|
|
|
If in doubt, say "N" and don't enable these drivers; most people
|
|
|
|
|
don't have this kind of hardware (except maybe inside Linux PDAs).
|
|
|
|
|
|
|
|
|
|
For more information, see <http://www.linux-usb.org/gadget> and
|
2017-05-16 11:11:58 -07:00
|
|
|
the kernel documentation for this API.
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2008-01-24 01:36:31 -07:00
|
|
|
if USB_GADGET
|
|
|
|
|
|
2007-07-01 17:35:28 -07:00
|
|
|
config USB_GADGET_DEBUG
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Debugging messages (DEVELOPMENT)"
|
2008-09-12 09:39:06 -07:00
|
|
|
depends on DEBUG_KERNEL
|
2007-07-01 17:35:28 -07:00
|
|
|
help
|
|
|
|
|
Many controller and gadget drivers will print some debugging
|
|
|
|
|
messages if you use this option to ask for those messages.
|
|
|
|
|
|
|
|
|
|
Avoid enabling these messages, even if you're actively
|
|
|
|
|
debugging such a driver. Many drivers will emit so many
|
2013-10-10 23:07:00 -07:00
|
|
|
messages that the driver timings are affected, which will
|
|
|
|
|
either create new failure modes or remove the one you're
|
|
|
|
|
trying to track down. Never enable these messages for a
|
|
|
|
|
production build.
|
|
|
|
|
|
|
|
|
|
config USB_GADGET_VERBOSE
|
|
|
|
|
bool "Verbose debugging Messages (DEVELOPMENT)"
|
|
|
|
|
depends on USB_GADGET_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Many controller and gadget drivers will print verbose debugging
|
|
|
|
|
messages if you use this option to ask for those messages.
|
|
|
|
|
|
|
|
|
|
Avoid enabling these messages, even if you're actively
|
|
|
|
|
debugging such a driver. Many drivers will emit so many
|
2007-07-01 17:35:28 -07:00
|
|
|
messages that the driver timings are affected, which will
|
|
|
|
|
either create new failure modes or remove the one you're
|
|
|
|
|
trying to track down. Never enable these messages for a
|
|
|
|
|
production build.
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
config USB_GADGET_DEBUG_FILES
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Debugging information files (DEVELOPMENT)"
|
2008-09-12 09:39:06 -07:00
|
|
|
depends on PROC_FS
|
2005-04-16 15:20:36 -07:00
|
|
|
help
|
|
|
|
|
Some of the drivers in the "gadget" framework can expose
|
|
|
|
|
debugging information in files such as /proc/driver/udc
|
|
|
|
|
(for a peripheral controller). The information in these
|
|
|
|
|
files may help when you're troubleshooting or bringing up a
|
|
|
|
|
driver on a new board. Enable these files by choosing "Y"
|
|
|
|
|
here. If in doubt, or to conserve kernel memory, say "N".
|
|
|
|
|
|
2007-10-10 02:29:43 -07:00
|
|
|
config USB_GADGET_DEBUG_FS
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Debugging information files in debugfs (DEVELOPMENT)"
|
2008-09-12 09:39:06 -07:00
|
|
|
depends on DEBUG_FS
|
2007-10-10 02:29:43 -07:00
|
|
|
help
|
|
|
|
|
Some of the drivers in the "gadget" framework can expose
|
|
|
|
|
debugging information in files under /sys/kernel/debug/.
|
|
|
|
|
The information in these files may help when you're
|
|
|
|
|
troubleshooting or bringing up a driver on a new board.
|
|
|
|
|
Enable these files by choosing "Y" here. If in doubt, or
|
|
|
|
|
to conserve kernel memory, say "N".
|
|
|
|
|
|
2008-09-12 09:39:06 -07:00
|
|
|
config USB_GADGET_VBUS_DRAW
|
|
|
|
|
int "Maximum VBUS Power usage (2-500 mA)"
|
|
|
|
|
range 2 500
|
|
|
|
|
default 2
|
|
|
|
|
help
|
|
|
|
|
Some devices need to draw power from USB when they are
|
|
|
|
|
configured, perhaps to operate circuitry or to recharge
|
|
|
|
|
batteries. This is in addition to any local power supply,
|
|
|
|
|
such as an AC adapter or batteries.
|
|
|
|
|
|
|
|
|
|
Enter the maximum power your device draws through USB, in
|
|
|
|
|
milliAmperes. The permitted range of values is 2 - 500 mA;
|
|
|
|
|
0 mA would be legal, but can make some hosts misbehave.
|
|
|
|
|
|
|
|
|
|
This value will be used except for system-specific gadget
|
|
|
|
|
drivers that have more specific information.
|
|
|
|
|
|
usb: gadget: storage: make FSG_NUM_BUFFERS variable size
FSG_NUM_BUFFERS is set to 2 as default.
Usually 2 buffers are enough to establish a good buffering pipeline.
The number may be increased in order to compensate a for bursty VFS
behaviour.
Here follows a description of system that may require more than
2 buffers.
* CPU ondemand governor active
* latency cost for wake up and/or frequency change
* DMA for IO
Use case description.
* Data transfer from MMC via VFS to USB.
* DMA shuffles data from MMC and to USB.
* The CPU wakes up every now and then to pass data in and out from VFS,
which cause the bursty VFS behaviour.
Test set up
* Running dd on the host reading from the mass storage device
* cmdline: dd if=/dev/sdb of=/dev/null bs=4k count=$((256*100))
* Caches are dropped on the host and on the device before each run
Measurements on a Snowball board with ondemand_governor active.
FSG_NUM_BUFFERS 2
104857600 bytes (105 MB) copied, 5.62173 s, 18.7 MB/s
104857600 bytes (105 MB) copied, 5.61811 s, 18.7 MB/s
104857600 bytes (105 MB) copied, 5.57817 s, 18.8 MB/s
FSG_NUM_BUFFERS 4
104857600 bytes (105 MB) copied, 5.26839 s, 19.9 MB/s
104857600 bytes (105 MB) copied, 5.2691 s, 19.9 MB/s
104857600 bytes (105 MB) copied, 5.2711 s, 19.9 MB/s
There may not be one optimal number for all boards. This is why
the number is added to Kconfig. If selecting USB_GADGET_DEBUG_FILES
this value may be set by a module parameter as well.
Signed-off-by: Per Forlin <per.forlin@linaro.org>
Acked-by: Michal Nazarewicz <mina86@mina86.com>
Acked-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Felipe Balbi <balbi@ti.com>
2011-08-19 12:21:27 -07:00
|
|
|
config USB_GADGET_STORAGE_NUM_BUFFERS
|
|
|
|
|
int "Number of storage pipeline buffers"
|
2016-05-12 05:02:29 -07:00
|
|
|
range 2 256
|
usb: gadget: storage: make FSG_NUM_BUFFERS variable size
FSG_NUM_BUFFERS is set to 2 as default.
Usually 2 buffers are enough to establish a good buffering pipeline.
The number may be increased in order to compensate a for bursty VFS
behaviour.
Here follows a description of system that may require more than
2 buffers.
* CPU ondemand governor active
* latency cost for wake up and/or frequency change
* DMA for IO
Use case description.
* Data transfer from MMC via VFS to USB.
* DMA shuffles data from MMC and to USB.
* The CPU wakes up every now and then to pass data in and out from VFS,
which cause the bursty VFS behaviour.
Test set up
* Running dd on the host reading from the mass storage device
* cmdline: dd if=/dev/sdb of=/dev/null bs=4k count=$((256*100))
* Caches are dropped on the host and on the device before each run
Measurements on a Snowball board with ondemand_governor active.
FSG_NUM_BUFFERS 2
104857600 bytes (105 MB) copied, 5.62173 s, 18.7 MB/s
104857600 bytes (105 MB) copied, 5.61811 s, 18.7 MB/s
104857600 bytes (105 MB) copied, 5.57817 s, 18.8 MB/s
FSG_NUM_BUFFERS 4
104857600 bytes (105 MB) copied, 5.26839 s, 19.9 MB/s
104857600 bytes (105 MB) copied, 5.2691 s, 19.9 MB/s
104857600 bytes (105 MB) copied, 5.2711 s, 19.9 MB/s
There may not be one optimal number for all boards. This is why
the number is added to Kconfig. If selecting USB_GADGET_DEBUG_FILES
this value may be set by a module parameter as well.
Signed-off-by: Per Forlin <per.forlin@linaro.org>
Acked-by: Michal Nazarewicz <mina86@mina86.com>
Acked-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Felipe Balbi <balbi@ti.com>
2011-08-19 12:21:27 -07:00
|
|
|
default 2
|
|
|
|
|
help
|
|
|
|
|
Usually 2 buffers are enough to establish a good buffering
|
|
|
|
|
pipeline. The number may be increased in order to compensate
|
|
|
|
|
for a bursty VFS behaviour. For instance there may be CPU wake up
|
|
|
|
|
latencies that makes the VFS to appear bursty in a system with
|
|
|
|
|
an CPU on-demand governor. Especially if DMA is doing IO to
|
|
|
|
|
offload the CPU. In this case the CPU will go into power
|
|
|
|
|
save often and spin up occasionally to move data within VFS.
|
|
|
|
|
If selecting USB_GADGET_DEBUG_FILES this value may be set by
|
|
|
|
|
a module parameter as well.
|
|
|
|
|
If unsure, say 2.
|
|
|
|
|
|
2015-11-21 00:44:53 -07:00
|
|
|
config U_SERIAL_CONSOLE
|
|
|
|
|
bool "Serial gadget console support"
|
2017-08-11 04:33:23 -07:00
|
|
|
depends on USB_U_SERIAL
|
2015-11-21 00:44:53 -07:00
|
|
|
help
|
|
|
|
|
It supports the serial gadget can be used as a console.
|
|
|
|
|
|
2014-07-15 04:09:45 -07:00
|
|
|
source "drivers/usb/gadget/udc/Kconfig"
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# USB Gadget Drivers
|
|
|
|
|
#
|
2012-09-06 11:11:09 -07:00
|
|
|
|
|
|
|
|
# composite based drivers
|
|
|
|
|
config USB_LIBCOMPOSITE
|
|
|
|
|
tristate
|
2012-12-23 13:10:24 -07:00
|
|
|
select CONFIGFS_FS
|
2012-09-06 11:11:09 -07:00
|
|
|
depends on USB_GADGET
|
|
|
|
|
|
2012-12-23 13:10:07 -07:00
|
|
|
config USB_F_ACM
|
|
|
|
|
tristate
|
|
|
|
|
|
2012-12-23 13:10:01 -07:00
|
|
|
config USB_F_SS_LB
|
|
|
|
|
tristate
|
|
|
|
|
|
2012-12-23 13:10:04 -07:00
|
|
|
config USB_U_SERIAL
|
|
|
|
|
tristate
|
|
|
|
|
|
usb: gadget: u_ether: convert into module
u_ether.c has been #include'd by all gadgets which implement
USB Ethernet functions. In order to add configfs support,
the f_ecm.c, f_eem.c, f_ncm.c, f_subset.c, f_rndis.c need to be
converted into modules and must not be #include'd. Consequently,
the u_ether.c needs to be a module too, in a manner similar
to u_serial.c. The resulting module should not take any parameters,
so they are pushed to the current users of it, that is ether.c,
g_ffs.c, multi.c, ncm.c, nokia.c.
Signed-off-by: Andrzej Pietrasiewicz <andrzej.p@samsung.com>
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
2013-05-23 00:22:03 -07:00
|
|
|
config USB_U_ETHER
|
|
|
|
|
tristate
|
|
|
|
|
|
2017-06-18 06:23:52 -07:00
|
|
|
config USB_U_AUDIO
|
|
|
|
|
tristate
|
|
|
|
|
|
2013-03-18 01:52:57 -07:00
|
|
|
config USB_F_SERIAL
|
2012-12-23 13:10:04 -07:00
|
|
|
tristate
|
|
|
|
|
|
2013-03-21 07:33:42 -07:00
|
|
|
config USB_F_OBEX
|
|
|
|
|
tristate
|
|
|
|
|
|
2013-05-23 00:22:06 -07:00
|
|
|
config USB_F_NCM
|
|
|
|
|
tristate
|
|
|
|
|
|
2013-05-23 01:32:03 -07:00
|
|
|
config USB_F_ECM
|
|
|
|
|
tristate
|
|
|
|
|
|
2013-05-23 01:51:11 -07:00
|
|
|
config USB_F_PHONET
|
|
|
|
|
tristate
|
|
|
|
|
|
2013-05-28 00:15:47 -07:00
|
|
|
config USB_F_EEM
|
|
|
|
|
tristate
|
|
|
|
|
|
2013-05-28 00:15:53 -07:00
|
|
|
config USB_F_SUBSET
|
|
|
|
|
tristate
|
|
|
|
|
|
2013-05-28 00:15:57 -07:00
|
|
|
config USB_F_RNDIS
|
|
|
|
|
tristate
|
|
|
|
|
|
2013-10-09 01:06:01 -07:00
|
|
|
config USB_F_MASS_STORAGE
|
|
|
|
|
tristate
|
|
|
|
|
|
2013-12-03 07:15:33 -07:00
|
|
|
config USB_F_FS
|
2024-01-30 05:23:39 -07:00
|
|
|
select DMA_SHARED_BUFFER
|
2013-12-03 07:15:33 -07:00
|
|
|
tristate
|
|
|
|
|
|
2017-06-18 06:23:54 -07:00
|
|
|
config USB_F_UAC1
|
|
|
|
|
tristate
|
|
|
|
|
|
2017-06-18 06:23:53 -07:00
|
|
|
config USB_F_UAC1_LEGACY
|
2014-07-22 10:58:38 -07:00
|
|
|
tristate
|
|
|
|
|
|
2014-07-22 10:58:30 -07:00
|
|
|
config USB_F_UAC2
|
|
|
|
|
tristate
|
|
|
|
|
|
2014-09-08 16:02:10 -07:00
|
|
|
config USB_F_UVC
|
|
|
|
|
tristate
|
2023-01-26 16:14:54 -07:00
|
|
|
select UVC_COMMON
|
2014-09-08 16:02:10 -07:00
|
|
|
|
2014-10-16 04:33:27 -07:00
|
|
|
config USB_F_MIDI
|
|
|
|
|
tristate
|
|
|
|
|
|
usb: gadget: Add support for USB MIDI 2.0 function driver
This patch adds the support for USB MIDI 2.0 gadget function driver.
The driver emulates a USB MIDI 2.0 interface with one or more UMP
Endpoints, where each of UMP Endpoint is a pair of MIDI Endpoints for
handling MIDI 2.0 UMP packets. When the function driver is bound, the
driver creates an ALSA card object with UMP rawmidi devices. This is
a kind of loop-back where the incoming and upcoming UMP packets
from/to the MIDI 2.0 UMP Endpoints are transferred as-is. In
addition, legacy (MIDI 1.0) rawmidi devices are created, so that
legacy applications can work in the gadget side, too.
When a USB MIDI 2.0 gadget interface appears, the connected host can
use it with the snd-usb-audio driver where MIDI 2.0 support is
enabled. Both gadget and connected hosts will have the similar UMP
Endpoint and Function Block (or Group Terminal Block) information.
Slight differences are the direction and UI-hint bits; it's due to the
nature of gadget driver, and the input/output direction is swapped in
both sides (the input for gadget is the output for host, and vice
versa).
The driver supports the brand-new UMP v1.1 feature, including the UMP
Stream message handling for providing UMP Endpoint and Function Block
information as well as dealing with the MIDI protocol switch. The
driver responds to UMP Stream messages by itself. OTOH, MIDI-CI
message handling isn't implemented in the kernel driver; it should be
processed in the user-space through the loopback UMP device.
As of this patch, the whole configuration is fixed, providing only one
bidirectional UMP Endpoint containing a single FB/GTB with a single
UMP Group. The configuration will be dynamically changeable in the
following patches.
The traditional MIDI 1.0 is still provided in the altset 0 (which is
mandatory per spec). But it's only about the configuration, and no
actual I/O will be running for the altset 0 as of this patch. The
proper support MIDI 1.0 altset will follow in later patches, too.
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Link: https://lore.kernel.org/r/20230725062206.9674-2-tiwai@suse.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2023-07-24 23:22:00 -07:00
|
|
|
config USB_F_MIDI2
|
|
|
|
|
tristate
|
|
|
|
|
|
2014-11-06 03:11:59 -07:00
|
|
|
config USB_F_HID
|
|
|
|
|
tristate
|
|
|
|
|
|
2015-03-03 02:52:28 -07:00
|
|
|
config USB_F_PRINTER
|
|
|
|
|
tristate
|
|
|
|
|
|
2015-12-11 08:06:21 -07:00
|
|
|
config USB_F_TCM
|
|
|
|
|
tristate
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
# this first set of drivers all depend on bulk-capable hardware.
|
|
|
|
|
|
2013-06-13 01:37:24 -07:00
|
|
|
config USB_CONFIGFS
|
2017-03-10 06:11:42 -07:00
|
|
|
tristate "USB Gadget functions configurable through configfs"
|
2013-06-13 01:37:24 -07:00
|
|
|
select USB_LIBCOMPOSITE
|
|
|
|
|
help
|
|
|
|
|
A Linux USB "gadget" can be set up through configfs.
|
|
|
|
|
If this is the case, the USB functions (which from the host's
|
|
|
|
|
perspective are seen as interfaces) and configurations are
|
|
|
|
|
specified simply by creating appropriate directories in configfs.
|
|
|
|
|
Associating functions with configurations is done by creating
|
|
|
|
|
appropriate symbolic links.
|
2019-06-18 14:05:38 -07:00
|
|
|
For more information see Documentation/usb/gadget_configfs.rst.
|
2013-06-13 01:37:24 -07:00
|
|
|
|
|
|
|
|
config USB_CONFIGFS_SERIAL
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Generic serial bulk in/out"
|
2013-06-13 01:37:24 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on TTY
|
|
|
|
|
select USB_U_SERIAL
|
|
|
|
|
select USB_F_SERIAL
|
|
|
|
|
help
|
|
|
|
|
The function talks to the Linux-USB generic serial driver.
|
|
|
|
|
|
|
|
|
|
config USB_CONFIGFS_ACM
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Abstract Control Model (CDC ACM)"
|
2013-06-13 01:37:24 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on TTY
|
|
|
|
|
select USB_U_SERIAL
|
|
|
|
|
select USB_F_ACM
|
|
|
|
|
help
|
|
|
|
|
ACM serial link. This function can be used to interoperate with
|
|
|
|
|
MS-Windows hosts or with the Linux-USB "cdc-acm" driver.
|
|
|
|
|
|
|
|
|
|
config USB_CONFIGFS_OBEX
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Object Exchange Model (CDC OBEX)"
|
2013-06-13 01:37:24 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on TTY
|
|
|
|
|
select USB_U_SERIAL
|
|
|
|
|
select USB_F_OBEX
|
|
|
|
|
help
|
|
|
|
|
You will need a user space OBEX server talking to /dev/ttyGS*,
|
|
|
|
|
since the kernel itself doesn't implement the OBEX protocol.
|
|
|
|
|
|
|
|
|
|
config USB_CONFIGFS_NCM
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Network Control Model (CDC NCM)"
|
2013-06-13 01:37:24 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on NET
|
|
|
|
|
select USB_U_ETHER
|
|
|
|
|
select USB_F_NCM
|
2021-01-03 14:42:17 -07:00
|
|
|
select CRC32
|
2013-06-13 01:37:24 -07:00
|
|
|
help
|
|
|
|
|
NCM is an advanced protocol for Ethernet encapsulation, allows
|
|
|
|
|
grouping of several ethernet frames into one USB transfer and
|
|
|
|
|
different alignment possibilities.
|
|
|
|
|
|
|
|
|
|
config USB_CONFIGFS_ECM
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Ethernet Control Model (CDC ECM)"
|
2013-06-13 01:37:24 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on NET
|
|
|
|
|
select USB_U_ETHER
|
|
|
|
|
select USB_F_ECM
|
|
|
|
|
help
|
|
|
|
|
The "Communication Device Class" (CDC) Ethernet Control Model.
|
|
|
|
|
That protocol is often avoided with pure Ethernet adapters, in
|
|
|
|
|
favor of simpler vendor-specific hardware, but is widely
|
|
|
|
|
supported by firmware for smart network devices.
|
|
|
|
|
|
2013-05-28 00:15:56 -07:00
|
|
|
config USB_CONFIGFS_ECM_SUBSET
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Ethernet Control Model (CDC ECM) subset"
|
2013-05-28 00:15:56 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on NET
|
|
|
|
|
select USB_U_ETHER
|
|
|
|
|
select USB_F_SUBSET
|
|
|
|
|
help
|
|
|
|
|
On hardware that can't implement the full protocol,
|
|
|
|
|
a simple CDC subset is used, placing fewer demands on USB.
|
|
|
|
|
|
2013-05-28 00:16:01 -07:00
|
|
|
config USB_CONFIGFS_RNDIS
|
|
|
|
|
bool "RNDIS"
|
|
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on NET
|
|
|
|
|
select USB_U_ETHER
|
|
|
|
|
select USB_F_RNDIS
|
|
|
|
|
help
|
|
|
|
|
Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
|
|
|
|
|
and Microsoft provides redistributable binary RNDIS drivers for
|
|
|
|
|
older versions of Windows.
|
|
|
|
|
|
|
|
|
|
To make MS-Windows work with this, use Documentation/usb/linux.inf
|
|
|
|
|
as the "driver info file". For versions of MS-Windows older than
|
|
|
|
|
XP, you'll need to download drivers from Microsoft's website; a URL
|
|
|
|
|
is given in comments found in that info file.
|
|
|
|
|
|
2013-05-28 00:15:51 -07:00
|
|
|
config USB_CONFIGFS_EEM
|
|
|
|
|
bool "Ethernet Emulation Model (EEM)"
|
|
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on NET
|
|
|
|
|
select USB_U_ETHER
|
|
|
|
|
select USB_F_EEM
|
2021-01-03 14:42:17 -07:00
|
|
|
select CRC32
|
2013-05-28 00:15:51 -07:00
|
|
|
help
|
|
|
|
|
CDC EEM is a newer USB standard that is somewhat simpler than CDC ECM
|
|
|
|
|
and therefore can be supported by more hardware. Technically ECM and
|
|
|
|
|
EEM are designed for different applications. The ECM model extends
|
|
|
|
|
the network interface to the target (e.g. a USB cable modem), and the
|
|
|
|
|
EEM model is for mobile devices to communicate with hosts using
|
|
|
|
|
ethernet over USB. For Linux gadgets, however, the interface with
|
|
|
|
|
the host is the same (a usbX device), so the differences are minimal.
|
|
|
|
|
|
2013-05-23 01:51:15 -07:00
|
|
|
config USB_CONFIGFS_PHONET
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Phonet protocol"
|
2013-05-23 01:51:15 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on NET
|
|
|
|
|
depends on PHONET
|
|
|
|
|
select USB_U_ETHER
|
|
|
|
|
select USB_F_PHONET
|
|
|
|
|
help
|
|
|
|
|
The Phonet protocol implementation for USB device.
|
|
|
|
|
|
2013-10-09 01:06:05 -07:00
|
|
|
config USB_CONFIGFS_MASS_STORAGE
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Mass storage"
|
2013-10-09 01:06:05 -07:00
|
|
|
depends on USB_CONFIGFS
|
2013-11-04 05:46:17 -07:00
|
|
|
depends on BLOCK
|
2013-10-09 01:06:05 -07:00
|
|
|
select USB_F_MASS_STORAGE
|
|
|
|
|
help
|
|
|
|
|
The Mass Storage Gadget acts as a USB Mass Storage disk drive.
|
|
|
|
|
As its storage repository it can use a regular file or a block
|
|
|
|
|
device (in much the same way as the "loop" device driver),
|
|
|
|
|
specified as a module parameter or sysfs option.
|
|
|
|
|
|
2013-11-07 00:41:28 -07:00
|
|
|
config USB_CONFIGFS_F_LB_SS
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Loopback and sourcesink function (for testing)"
|
2013-11-07 00:41:27 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
select USB_F_SS_LB
|
|
|
|
|
help
|
2013-11-07 00:41:28 -07:00
|
|
|
Loopback function loops back a configurable number of transfers.
|
|
|
|
|
Sourcesink function either sinks and sources bulk data.
|
2013-11-07 00:41:27 -07:00
|
|
|
It also implements control requests, for "chapter 9" conformance.
|
|
|
|
|
Make this be the first driver you try using on top of any new
|
|
|
|
|
USB peripheral controller driver. Then you can use host-side
|
|
|
|
|
test software, like the "usbtest" driver, to put your hardware
|
|
|
|
|
and its driver through a basic set of functional tests.
|
|
|
|
|
|
2013-12-03 07:15:36 -07:00
|
|
|
config USB_CONFIGFS_F_FS
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Function filesystem (FunctionFS)"
|
2013-12-03 07:15:36 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
select USB_F_FS
|
|
|
|
|
help
|
|
|
|
|
The Function Filesystem (FunctionFS) lets one create USB
|
|
|
|
|
composite functions in user space in the same way GadgetFS
|
|
|
|
|
lets one create USB gadgets in user space. This allows creation
|
|
|
|
|
of composite gadgets such that some of the functions are
|
|
|
|
|
implemented in kernel space (for instance Ethernet, serial or
|
|
|
|
|
mass storage) and other are implemented in user space.
|
|
|
|
|
|
2017-06-18 06:23:54 -07:00
|
|
|
config USB_CONFIGFS_F_UAC1
|
|
|
|
|
bool "Audio Class 1.0"
|
|
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on SND
|
|
|
|
|
select USB_LIBCOMPOSITE
|
|
|
|
|
select SND_PCM
|
|
|
|
|
select USB_U_AUDIO
|
|
|
|
|
select USB_F_UAC1
|
|
|
|
|
help
|
|
|
|
|
This Audio function implements 1 AudioControl interface,
|
|
|
|
|
1 AudioStreaming Interface each for USB-OUT and USB-IN.
|
|
|
|
|
This driver doesn't expect any real Audio codec to be present
|
|
|
|
|
on the device - the audio streams are simply sinked to and
|
|
|
|
|
sourced from a virtual ALSA sound card created. The user-space
|
|
|
|
|
application may choose to do whatever it wants with the data
|
|
|
|
|
received from the USB Host and choose to provide whatever it
|
|
|
|
|
wants as audio data to the USB Host.
|
|
|
|
|
|
2017-06-18 06:23:53 -07:00
|
|
|
config USB_CONFIGFS_F_UAC1_LEGACY
|
|
|
|
|
bool "Audio Class 1.0 (legacy implementation)"
|
2014-10-16 04:16:28 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on SND
|
|
|
|
|
select USB_LIBCOMPOSITE
|
|
|
|
|
select SND_PCM
|
2017-06-18 06:23:53 -07:00
|
|
|
select USB_F_UAC1_LEGACY
|
2014-10-16 04:16:28 -07:00
|
|
|
help
|
|
|
|
|
This Audio function implements 1 AudioControl interface,
|
|
|
|
|
1 AudioStreaming Interface each for USB-OUT and USB-IN.
|
2017-06-18 06:23:54 -07:00
|
|
|
This is a legacy driver and requires a real Audio codec
|
|
|
|
|
to be present on the device.
|
2014-10-16 04:16:28 -07:00
|
|
|
|
|
|
|
|
config USB_CONFIGFS_F_UAC2
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "Audio Class 2.0"
|
2014-10-16 04:16:28 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on SND
|
|
|
|
|
select USB_LIBCOMPOSITE
|
|
|
|
|
select SND_PCM
|
2017-06-18 06:23:52 -07:00
|
|
|
select USB_U_AUDIO
|
2014-10-16 04:16:28 -07:00
|
|
|
select USB_F_UAC2
|
|
|
|
|
help
|
|
|
|
|
This Audio function is compatible with USB Audio Class
|
|
|
|
|
specification 2.0. It implements 1 AudioControl interface,
|
|
|
|
|
1 AudioStreaming Interface each for USB-OUT and USB-IN.
|
|
|
|
|
This driver doesn't expect any real Audio codec to be present
|
|
|
|
|
on the device - the audio streams are simply sinked to and
|
|
|
|
|
sourced from a virtual ALSA sound card created. The user-space
|
|
|
|
|
application may choose to do whatever it wants with the data
|
|
|
|
|
received from the USB Host and choose to provide whatever it
|
|
|
|
|
wants as audio data to the USB Host.
|
|
|
|
|
|
2014-10-16 04:33:31 -07:00
|
|
|
config USB_CONFIGFS_F_MIDI
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "MIDI function"
|
2014-10-16 04:33:31 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on SND
|
|
|
|
|
select USB_LIBCOMPOSITE
|
|
|
|
|
select SND_RAWMIDI
|
|
|
|
|
select USB_F_MIDI
|
|
|
|
|
help
|
|
|
|
|
The MIDI Function acts as a USB Audio device, with one MIDI
|
|
|
|
|
input and one MIDI output. These MIDI jacks appear as
|
|
|
|
|
a sound "card" in the ALSA sound system. Other MIDI
|
|
|
|
|
connections can then be made on the gadget system, using
|
|
|
|
|
ALSA's aconnect utility etc.
|
|
|
|
|
|
usb: gadget: Add support for USB MIDI 2.0 function driver
This patch adds the support for USB MIDI 2.0 gadget function driver.
The driver emulates a USB MIDI 2.0 interface with one or more UMP
Endpoints, where each of UMP Endpoint is a pair of MIDI Endpoints for
handling MIDI 2.0 UMP packets. When the function driver is bound, the
driver creates an ALSA card object with UMP rawmidi devices. This is
a kind of loop-back where the incoming and upcoming UMP packets
from/to the MIDI 2.0 UMP Endpoints are transferred as-is. In
addition, legacy (MIDI 1.0) rawmidi devices are created, so that
legacy applications can work in the gadget side, too.
When a USB MIDI 2.0 gadget interface appears, the connected host can
use it with the snd-usb-audio driver where MIDI 2.0 support is
enabled. Both gadget and connected hosts will have the similar UMP
Endpoint and Function Block (or Group Terminal Block) information.
Slight differences are the direction and UI-hint bits; it's due to the
nature of gadget driver, and the input/output direction is swapped in
both sides (the input for gadget is the output for host, and vice
versa).
The driver supports the brand-new UMP v1.1 feature, including the UMP
Stream message handling for providing UMP Endpoint and Function Block
information as well as dealing with the MIDI protocol switch. The
driver responds to UMP Stream messages by itself. OTOH, MIDI-CI
message handling isn't implemented in the kernel driver; it should be
processed in the user-space through the loopback UMP device.
As of this patch, the whole configuration is fixed, providing only one
bidirectional UMP Endpoint containing a single FB/GTB with a single
UMP Group. The configuration will be dynamically changeable in the
following patches.
The traditional MIDI 1.0 is still provided in the altset 0 (which is
mandatory per spec). But it's only about the configuration, and no
actual I/O will be running for the altset 0 as of this patch. The
proper support MIDI 1.0 altset will follow in later patches, too.
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Link: https://lore.kernel.org/r/20230725062206.9674-2-tiwai@suse.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2023-07-24 23:22:00 -07:00
|
|
|
config USB_CONFIGFS_F_MIDI2
|
|
|
|
|
bool "MIDI 2.0 function"
|
|
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
depends on SND
|
|
|
|
|
select USB_LIBCOMPOSITE
|
|
|
|
|
select SND_UMP
|
|
|
|
|
select SND_UMP_LEGACY_RAWMIDI
|
|
|
|
|
select USB_F_MIDI2
|
|
|
|
|
help
|
|
|
|
|
The MIDI 2.0 function driver provides the generic emulated
|
|
|
|
|
USB MIDI 2.0 interface, looped back to ALSA UMP rawmidi
|
|
|
|
|
device on the gadget host. It supports UMP 1.1 spec and
|
|
|
|
|
responds UMP Stream messages for UMP Endpoint and Function
|
|
|
|
|
Block information / configuration.
|
|
|
|
|
|
2014-11-06 03:12:03 -07:00
|
|
|
config USB_CONFIGFS_F_HID
|
2014-12-20 13:41:11 -07:00
|
|
|
bool "HID function"
|
2014-11-06 03:12:03 -07:00
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
select USB_F_HID
|
|
|
|
|
help
|
|
|
|
|
The HID function driver provides generic emulation of USB
|
|
|
|
|
Human Interface Devices (HID).
|
|
|
|
|
|
2019-06-18 14:05:38 -07:00
|
|
|
For more information, see Documentation/usb/gadget_hid.rst.
|
2014-11-06 03:12:03 -07:00
|
|
|
|
2014-12-10 04:34:02 -07:00
|
|
|
config USB_CONFIGFS_F_UVC
|
2015-02-02 08:00:03 -07:00
|
|
|
bool "USB Webcam function"
|
2014-12-10 04:34:02 -07:00
|
|
|
depends on USB_CONFIGFS
|
media: Kconfig: cleanup VIDEO_DEV dependencies
media Kconfig has two entries associated to V4L API:
VIDEO_DEV and VIDEO_V4L2.
On Kernel 2.6.x, there were two V4L APIs, each one with its own flag.
VIDEO_DEV were meant to:
1) enable Video4Linux and make its Kconfig options to appear;
2) it makes the Kernel build the V4L core.
while VIDEO_V4L2 where used to distinguish between drivers that
implement the newer API and drivers that implemented the former one.
With time, such meaning changed, specially after the removal of
all V4L version 1 drivers.
At the current implementation, VIDEO_DEV only does (1): it enables
the media options related to V4L, that now has:
menu "Video4Linux options"
visible if VIDEO_DEV
source "drivers/media/v4l2-core/Kconfig"
endmenu
but it doesn't affect anymore the V4L core drivers.
The rationale is that the V4L2 core has a "soft" dependency
at the I2C bus, and now requires to select a number of other
Kconfig options:
config VIDEO_V4L2
tristate
depends on (I2C || I2C=n) && VIDEO_DEV
select RATIONAL
select VIDEOBUF2_V4L2 if VIDEOBUF2_CORE
default (I2C || I2C=n) && VIDEO_DEV
In the past, merging them would be tricky, but it seems that it is now
possible to merge those symbols, in order to simplify V4L dependencies.
Let's keep VIDEO_DEV, as this one is used on some make *defconfig
configurations.
Suggested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Jacopo Mondi <jacopo@jmondi.org>
Reviewed-by: Neil Armstrong <narmstrong@baylibre.com> # for meson-vdec & meson-ge2d
Acked-by: Andrzej Pietrasiewicz <andrzejtp2010@gmail.com>
Acked-by: Łukasz Stelmach <l.stelmach@samsung.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
2022-03-12 23:25:46 -07:00
|
|
|
depends on VIDEO_DEV
|
2014-12-10 04:34:02 -07:00
|
|
|
depends on VIDEO_DEV
|
2021-06-28 08:53:10 -07:00
|
|
|
select VIDEOBUF2_DMA_SG
|
2014-12-10 04:34:02 -07:00
|
|
|
select VIDEOBUF2_VMALLOC
|
|
|
|
|
select USB_F_UVC
|
|
|
|
|
help
|
|
|
|
|
The Webcam function acts as a composite USB Audio and Video Class
|
|
|
|
|
device. It provides a userspace API to process UVC control requests
|
|
|
|
|
and stream video data to the host.
|
|
|
|
|
|
2015-03-03 02:52:32 -07:00
|
|
|
config USB_CONFIGFS_F_PRINTER
|
|
|
|
|
bool "Printer function"
|
|
|
|
|
select USB_F_PRINTER
|
2015-03-24 02:58:16 -07:00
|
|
|
depends on USB_CONFIGFS
|
2015-03-03 02:52:32 -07:00
|
|
|
help
|
|
|
|
|
The Printer function channels data between the USB host and a
|
|
|
|
|
userspace program driving the print engine. The user space
|
|
|
|
|
program reads and writes the device file /dev/g_printer<X> to
|
|
|
|
|
receive or send printer data. It can use ioctl calls to
|
|
|
|
|
the device file to get or set printer status.
|
|
|
|
|
|
2019-06-18 14:05:38 -07:00
|
|
|
For more information, see Documentation/usb/gadget_printer.rst
|
2015-03-03 02:52:32 -07:00
|
|
|
which includes sample code for accessing the device file.
|
|
|
|
|
|
2015-12-11 08:06:26 -07:00
|
|
|
config USB_CONFIGFS_F_TCM
|
|
|
|
|
bool "USB Gadget Target Fabric"
|
|
|
|
|
depends on TARGET_CORE
|
|
|
|
|
depends on USB_CONFIGFS
|
|
|
|
|
select USB_LIBCOMPOSITE
|
|
|
|
|
select USB_F_TCM
|
|
|
|
|
help
|
|
|
|
|
This fabric is a USB gadget component. Two USB protocols are
|
|
|
|
|
supported that is BBB or BOT (Bulk Only Transport) and UAS
|
|
|
|
|
(USB Attached SCSI). BOT is advertised on alternative
|
|
|
|
|
interface 0 (primary) and UAS is on alternative interface 1.
|
|
|
|
|
Both protocols can work on USB2.0 and USB3.0.
|
|
|
|
|
UAS utilizes the USB 3.0 feature called streams support.
|
|
|
|
|
|
2017-10-31 11:03:19 -07:00
|
|
|
source "drivers/usb/gadget/legacy/Kconfig"
|
|
|
|
|
|
2008-01-24 01:36:31 -07:00
|
|
|
endif # USB_GADGET
|