Documentation/admin-guide/media/usb-cardlist.rst
Source file repositories/reference/linux-study-clean/Documentation/admin-guide/media/usb-cardlist.rst
File Facts
- System
- Linux kernel
- Corpus path
Documentation/admin-guide/media/usb-cardlist.rst- Extension
.rst- Size
- 5558 bytes
- Lines
- 150
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: documentation
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
.. SPDX-License-Identifier: GPL-2.0
USB drivers
===========
The USB boards are identified by an identification called USB ID.
The ``lsusb`` command allows identifying the USB IDs::
$ lsusb
...
Bus 001 Device 015: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
Bus 001 Device 074: ID 2040:b131 Hauppauge
Bus 001 Device 075: ID 2013:024f PCTV Systems nanoStick T2 290e
...
Newer camera devices use a standard way to expose themselves as such,
via USB Video Class. Those cameras are automatically supported by the
``uvc-driver``.
Older cameras and TV USB devices uses USB Vendor Classes: each vendor
defines its own way to access the device. This section contains
card lists for such vendor-class devices.
While this is not as common as on PCI, sometimes the same USB ID is used
by different products. So, several media drivers allow passing a ``card=``
parameter, in order to setup a card number that would match the correct
settings for an specific product type.
The current supported USB cards (not including staging drivers) are
listed below\ [#]_.
.. [#]
some of the drivers have sub-drivers, not shown at this table.
In particular, gspca driver has lots of sub-drivers,
for cameras not supported by the USB Video Class (UVC) driver,
as shown at :doc:`gspca card list <gspca-cardlist>`.
====================== =========================================================
Driver Name
====================== =========================================================
airspy AirSpy
au0828 Auvitek AU0828
b2c2-flexcop-usb Technisat/B2C2 Air/Sky/Cable2PC USB
cx231xx Conexant cx231xx USB video capture
dvb-as102 Abilis AS102 DVB receiver
dvb-ttusb-budget Technotrend/Hauppauge Nova - USB devices
dvb-usb-a800 AVerMedia AverTV DVB-T USB 2.0 (A800)
dvb-usb-af9005 Afatech AF9005 DVB-T USB1.1
dvb-usb-af9015 Afatech AF9015 DVB-T USB2.0
dvb-usb-af9035 Afatech AF9035 DVB-T USB2.0
dvb-usb-anysee Anysee DVB-T/C USB2.0
dvb-usb-au6610 Alcor Micro AU6610 USB2.0
dvb-usb-az6007 AzureWave 6007 and clones DVB-T/C USB2.0
dvb-usb-az6027 Azurewave DVB-S/S2 USB2.0 AZ6027
dvb-usb-ce6230 Intel CE6230 DVB-T USB2.0
dvb-usb-cinergyT2 Terratec CinergyT2/qanu USB 2.0 DVB-T
dvb-usb-cxusb Conexant USB2.0 hybrid
dvb-usb-dib0700 DiBcom DiB0700
dvb-usb-dibusb-common DiBcom DiB3000M-B
dvb-usb-dibusb-mc DiBcom DiB3000M-C/P
dvb-usb-digitv Nebula Electronics uDigiTV DVB-T USB2.0
dvb-usb-dtt200u WideView WT-200U and WT-220U (pen) DVB-T
dvb-usb-dtv5100 AME DTV-5100 USB2.0 DVB-T
dvb-usb-dvbsky DVBSky USB
dvb-usb-dw2102 DvbWorld & TeVii DVB-S/S2 USB2.0
dvb-usb-ec168 E3C EC168 DVB-T USB2.0
dvb-usb-gl861 Genesys Logic GL861 USB2.0
dvb-usb-gp8psk GENPIX 8PSK->USB module
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.