Home
last modified time | relevance | path

Searched +full:usb +full:- +full:based (Results 1 – 25 of 899) sorted by relevance

12345678910>>...36

/linux/drivers/net/usb/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # USB Network devices configuration
5 comment "Host-side USB support is needed for USB Network Adapter support"
6 depends on !USB && NET
9 tristate "USB Network Adapters"
10 default USB if USB
11 depends on USB && NET
16 tristate "USB CATC NetMate-based Ethernet device support"
19 Say Y if you want to use one of the following 10Mbps USB Ethernet
20 device based on the EL1210A chip. Supported devices are:
[all …]
/linux/drivers/media/usb/gspca/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "GSPCA based webcams"
8 Say Y here if you want to enable selecting webcams based
11 See <file:Documentation/admin-guide/media/gspca-cardlist.rst> for more info.
22 tristate "Benq USB Camera Driver"
34 Say Y here if you want support for cameras based on the Conexant chip.
43 Say Y here if you want support for USB cameras based on the cpia
51 tristate "DTCS033 (Scopium) USB Astro-Camera Driver"
61 tristate "Etoms USB Camera Driver"
64 Say Y here if you want support for cameras based on the Etoms chip.
[all …]
/linux/drivers/usb/storage/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 # USB Storage driver configuration
10 tristate "USB Mass Storage support"
13 Say Y here if you want to connect USB mass storage devices to your
14 computer's USB port. This is the driver you need for USB
15 floppy drives, USB hard disks, USB tape drives, USB CD-ROMs,
16 USB flash devices, and memory sticks, along with
22 (BLK_DEV_SD) for most USB storage devices.
25 module will be called usb-storage.
30 bool "USB Mass Storage verbose debug"
[all …]
H A Dunusual_datafab.h1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Unusual Devices File for the Datafab USB Compact Flash reader
11 "MDCFE-B USB CF Reader",
16 * The following Datafab-based devices may or may not work
23 * other Datafab-based cards operational with this driver, I've decided
41 "Datafab-based Reader",
47 "Datafab-based Reader",
66 "USB to CF + SM Combo (LC1)",
73 * as "DualSlot CompactFlash(TM) & MStick Drive USB"
77 "USB CF+MS",
/linux/drivers/media/usb/dvb-usb/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "Support for various USB DVB devices"
4 depends on DVB_CORE && USB && I2C && RC_CORE
10 Almost every USB device needs a firmware, please look into
11 <file:Documentation/driver-api/media/drivers/dvb-usb.rst>.
13 For a complete list of supported USB devices see the LinuxTV DVB Wiki:
16 Say Y if you own a USB DVB device.
19 bool "Enable extended debug support for all DVB-USB devices"
22 Say Y if you want to enable debugging. See modinfo dvb-usb (and the
28 tristate "AVerMedia AverTV DVB-T USB 2.0 (A800)"
[all …]
/linux/Documentation/usb/
H A Draw-gadget.rst2 USB Raw Gadget
5 USB Raw Gadget is a gadget driver that gives userspace low-level control over
8 Like any other gadget driver, Raw Gadget implements USB devices via the
9 USB gadget API. Unlike most gadget drivers, Raw Gadget does not implement
10 any concrete USB functions itself but requires userspace to do that.
21 USB gadget layer for userspace. The key differences are:
23 1. Raw Gadget passes every USB request to userspace to get a response, while
24 GadgetFS responds to some USB requests internally based on the provided
28 2. Raw Gadget allows providing arbitrary data as responses to USB requests,
29 while GadgetFS performs sanity checks on the provided USB descriptors.
[all …]
/linux/drivers/usb/serial/
H A Dio_usbvend.h1 /* SPDX-License-Identifier: GPL-2.0+ */
4 * USBVEND.H Vendor-specific USB definitions
7 * must be kept backward-compatible with older firmware.
25 // Definitions of USB product IDs
33 // Definitions of USB product IDs (PID)
34 // We break the USB-defined PID into an OEM Id field (upper 6 bits)
40 // ION-device OEM IDs
50 // ION-device Device IDs
51 // Product IDs - assigned to match middle digit of serial number (No longer true)
54 // is based on the 80251+Netchip.
[all …]
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 # USB Serial device configuration
7 tristate "USB Serial Converter support"
10 Say Y here if you have a USB device that provides normal serial
12 your USB bus.
14 Please read <file:Documentation/usb/usb-serial.rst> for more
24 bool "USB Serial Console device support"
27 If you say Y here, it will be possible to use a USB to serial
41 kernel will automatically use the first USB to serial converter
47 bool "USB Generic Serial Driver"
[all …]
/linux/drivers/usb/core/
H A Dof.c1 // SPDX-License-Identifier: GPL-2.0
12 #include <linux/usb/of.h>
15 * usb_of_get_device_node() - get a USB device node
17 * @port1: one-based index of port
19 * Look up the node of a USB device given its parent hub device and one-based
30 for_each_child_of_node(hub->dev.of_node, node) { in usb_of_get_device_node()
43 * usb_of_has_combined_node() - determine whether a device has a combined node
44 * @udev: USB device
46 * Determine whether a USB device has a so called combined node which is
59 struct usb_device_descriptor *ddesc = &udev->descriptor; in usb_of_has_combined_node()
[all …]
/linux/drivers/bluetooth/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
27 tristate "HCI USB driver"
28 depends on USB
31 Bluetooth HCI USB driver.
33 USB interface.
35 Say Y here to compile support for Bluetooth USB devices into the
39 bool "Enable USB autosuspend for Bluetooth USB devices by default"
42 Say Y here to enable USB autosuspend for Bluetooth USB devices by
49 bool "Enable USB poll_sync for Bluetooth USB devices by default"
53 poll_sync synchronizes the USB data and event endpoints by
[all …]
/linux/Documentation/admin-guide/media/
H A Dtechnisat.rst1 .. SPDX-License-Identifier: GPL-2.0
13 -----------------------------
15 Important Notice: The driver does NOT support Technisat USB 2 devices!
19 .. code-block:: none
21 lspci -vvv for a PCI device (lsusb -vvv for an USB device) will show you for example:
29 -------------------
37 (except ``Simple tuner support`` for ATSC 3rd generation only -> see case 9 please).
41 - Main module part:
46 #) => ``Technisat/B2C2 Air/Sky/Cable2PC USB`` (USB 1.1 adapter)
50 - Frontend / Tuner / Demodulator module part:
[all …]
/linux/drivers/usb/common/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
8 bool "USB LED Triggers"
11 This option adds LED triggers for USB host and/or gadget activity.
13 Say Y here if you are working on a system with led-class supported
14 LEDs and you want to use them as activity indicators for USB host or
18 tristate "USB ULPI PHY interface support"
22 USB 2.0 PHY interface. The ULPI specification defines a standard set
27 The ULPI interfaces (the buses) are registered by the drivers for USB
33 protocol) and USB charger detection.
39 tristate "USB GPIO Based Connection Detection Driver"
[all …]
/linux/drivers/net/wireless/intersil/p54/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
8 This is common code for isl38xx/stlc45xx based modules.
9 This module does nothing by itself - the USB/PCI/SPI front-ends
18 tristate "Prism54 USB support"
19 depends on P54_COMMON && USB
22 This driver is for USB isl38xx based wireless cards.
33 This driver is for PCI isl38xx based wireless cards.
47 This driver is for stlc4550 or stlc4560 based wireless chips
57 Unlike the PCI or USB devices, the SPI variants don't have
/linux/drivers/usb/typec/tcpm/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Port Controller Manager"
5 depends on USB
9 The Type-C Port Controller Manager provides a USB PD and USB Type-C
10 state machine for use with Type-C Port Controllers.
15 tristate "Type-C Port Controller Interface driver"
19 Type-C Port Controller driver for TCPCI-compliant controller.
24 tristate "Richtek RT1711H Type-C chip driver"
26 Richtek RT1711H Type-C chip driver that works with
27 Type-C Port Controller Manager to provide USB PD and USB
[all …]
/linux/drivers/net/wireless/realtek/rtl818x/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
10 This is a driver for RTL8180, RTL8185 and RTL8187SE based cards.
11 These are PCI based chips found in cards such as:
14 A-Link WL54PC
19 Dlink DWL-610
20 Dlink DWL-510
22 Level-One WPC-0101
24 VCTnet PC-11B1
25 Ovislink AirLive WL-1120PCM
26 Mentor WL-PCI
[all …]
/linux/Documentation/devicetree/bindings/net/
H A Dmarvell-bt-8xxx.txt1 Marvell 8897/8997 (sd8897/sd8997) bluetooth devices (SDIO or USB based)
2 ------
4 the btmrvl driver is used and when used on USB interface, the btusb driver is
9 - compatible : should be one of the following:
10 * "marvell,sd8897-bt" (for SDIO)
11 * "marvell,sd8997-bt" (for SDIO)
12 * "usb1286,204e" (for USB)
16 - marvell,cal-data: Calibration data downloaded to the device during
20 - marvell,wakeup-pin: It represents wakeup pin number of the bluetooth chip.
22 - marvell,wakeup-gap-ms: wakeup gap represents wakeup latency of the host
[all …]
/linux/drivers/net/wireless/ath/ath6kl/
H A DKconfig1 # SPDX-License-Identifier: ISC
6 This module adds core support for wireless adapters based on
8 bus drivers for USB and SDIO to be able to use real devices.
19 This module adds support for wireless adapters based on
26 tristate "Atheros ath6kl USB support"
28 depends on USB
30 This module adds support for wireless adapters based on
31 Atheros AR6004 chipset and chipsets based on it running over
32 USB. If you choose to build it as a module, it will be
51 example, can be enabled with help of trace-cmd. All debug
/linux/drivers/usb/atm/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 # USB/ATM DSL configuration
7 tristate "USB DSL modem support"
11 Say Y here if you want to connect a USB Digital Subscriber Line (DSL)
12 modem to your computer's USB port. You will then need to choose your
21 tristate "Speedtouch USB support"
24 Say Y here if you have an SpeedTouch USB or SpeedTouch 330
27 <http://www.linux-usb.org/SpeedTouch/> for details.
33 tristate "Conexant AccessRunner USB support"
36 Say Y here if you have an ADSL USB modem based on the Conexant
[all …]
/linux/drivers/usb/dwc3/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
5 depends on (USB || USB_GADGET) && HAS_DMA
11 USB controller based on the DesignWare USB3 IP Core.
27 default USB_DWC3_DUAL_ROLE if (USB && USB_GADGET)
28 default USB_DWC3_HOST if (USB && !USB_GADGET)
29 default USB_DWC3_GADGET if (!USB && USB_GADGET)
33 depends on USB=y || USB=USB_DWC3
47 depends on ((USB=y || USB=USB_DWC3) && (USB_GADGET=y || USB_GADGET=USB_DWC3))
78 tristate "PCIe-based Platforms"
86 tristate "Synopsys PCIe-based HAPS Platforms"
[all …]
/linux/drivers/media/rc/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
80 tristate "Enable IR raw decoder for the RC-5 protocol"
84 Enable this option if you have IR with RC-5 protocol, and
96 tristate "Enable IR raw decoder for the RC-MM protocol"
98 Enable this option when you have IR with RC-MM protocol, and
100 24 and 32 bits RC-MM variants. You can enable or disable the
102 'rc-mm-12', 'rc-mm-24' and 'rc-mm-32'.
105 will be called ir-rcmm-decoder.
172 module will be called fintek-cir.
178 Say Y if you want to use GPIO based IR Receiver.
[all …]
/linux/drivers/usb/phy/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 # Physical Layer USB driver configuration
5 menu "USB Physical Layer drivers"
12 # USB Transceiver Drivers
15 tristate "AB8500 USB Transceiver Driver"
19 Enable this to support the USB OTG transceiver in AB8500 chip.
24 tristate "Freescale USB OTG Transceiver Driver"
29 Enable this to support Freescale USB OTG transceiver.
32 tristate "Keystone USB PHY Driver"
36 Enable this to support Keystone USB phy. This driver provides
[all …]
/linux/drivers/media/usb/cx231xx/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "Conexant cx231xx USB video capture support"
12 This is a video4linux driver for Conexant 231xx USB based TV cards.
27 ones used with ISDB-T boards.
37 This is an ALSA driver for Cx231xx USB based TV cards.
40 module will be called cx231xx-alsa
43 tristate "DVB/ATSC Support for Cx231xx based TV cards"
58 This adds support for DVB cards based on the
/linux/Documentation/sound/designs/
H A Dmidi-2.0.rst12 - Support of Universal MIDI Packet (UMP)
13 - Support of MIDI 2.0 protocol messages
14 - Transparent conversions between UMP and legacy MIDI 1.0 byte stream
15 - MIDI-CI for property and profile configurations
26 MIDI-CI is a high-level protocol that can talk with the MIDI device
31 the encoding/decoding of MIDI protocols on UMP, while MIDI-CI is
32 supported in user-space over the standard SysEx.
34 As of this writing, only USB MIDI device supports the UMP and Linux
62 Rawmidi Device with USB MIDI 2.0
65 When a device supports MIDI 2.0, the USB-audio driver probes and uses
[all …]
/linux/drivers/usb/musb/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
3 # USB Dual Role (OTG-ready) Controller Drivers
4 # for silicon based on Mentor Graphics INVENTRA designs
7 # (M)HDRC = (Multipoint) Highspeed Dual-Role Controller
10 depends on (USB || USB_GADGET)
13 Say Y here if your system has a dual role high speed USB
14 controller based on the Mentor Graphics silicon IP. Then
16 it's being used with, including the USB peripheral role,
17 or the USB host role, or both.
27 module will be called "musb-hdrc".
[all …]
/linux/drivers/phy/samsung/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
15 tristate "S5P/Exynos SoC series MIPI CSI-2/DSI PHY driver"
21 Support for MIPI CSI-2 and MIPI DSI DPHY found on Samsung S5P
42 tristate "S5P/Exynos SoC series USB 2.0 PHY driver"
49 Enable this to support the Samsung USB 2.0 PHY driver for Samsung
50 S5Pv210 and Exynos SoCs. This driver provides the interface for USB
51 2.0 PHY. Support for particular PHYs will be enabled based on the SoC
74 Enable USB PHY support for S5PV210. This option requires that Samsung
75 USB 2.0 PHY driver is enabled and means that support for this
77 are available - device and host.
[all …]

12345678910>>...36