Linux中如何查看usb設備信息
更新時間：2023年06月01日 10:38:25 作者：www.wowothink.com
這篇文章主要介紹了Linux中如何查看usb設備信息問題，具有很好的參考價值，希望對大家有所幫助。如有錯誤或未考慮完全的地方，望不吝賜教
下面的信息都是在VMware中運行Ubuntu12-04系統(tǒng)上執(zhí)行的。
同樣該命令也支持在嵌入式系統(tǒng)中進行USB調試。
一、cat設備節(jié)點獲取信息
在一些嵌入式開發(fā)中需要調試USB功能，經常會cat /sys 下的相關設備節(jié)點來查看某些信息，比如說我們可以看到 /sys/bus/usb/devices 目錄有多個子目錄。
進入到某個子目錄可以看到usb設備更加詳細的信息(可以理解為設備描述符)。
1、usb設備在總線上的信息
// usb設備在總線上的信息 root@ubuntu:/sys/kernel/debug# cd /sys/bus/usb/devices root@ubuntu:/sys/bus/usb/devices# ll total 0 drwxr-xr-x 2 root root 0 Nov 26 21:21 ./ drwxr-xr-x 4 root root 0 Nov 26 21:21 ../ lrwxrwxrwx 1 root root 0 Nov 26 21:21 1-0:1.0 -> ../../../devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-0:1.0/ lrwxrwxrwx 1 root root 0 Dec 15 23:10 1-1 -> ../../../devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1/ lrwxrwxrwx 1 root root 0 Dec 15 23:18 1-1:1.0 -> ../../../devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1/1-1:1.0/ lrwxrwxrwx 1 root root 0 Nov 26 21:21 2-0:1.0 -> ../../../devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-0:1.0/ lrwxrwxrwx 1 root root 0 Nov 26 21:21 2-1 -> ../../../devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/ lrwxrwxrwx 1 root root 0 Nov 26 21:21 2-1:1.0 -> ../../../devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.0/ lrwxrwxrwx 1 root root 0 Nov 26 21:21 2-2 -> ../../../devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-2/ lrwxrwxrwx 1 root root 0 Nov 26 21:21 2-2:1.0 -> ../../../devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-2/2-2:1.0/ lrwxrwxrwx 1 root root 0 Nov 26 21:21 usb1 -> ../../../devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/ lrwxrwxrwx 1 root root 0 Nov 26 21:21 usb2 -> ../../../devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/
其中 usbx/第x個總線，x-y:a.b/的目錄格式，x表示總線號，y表示端口，a表示配置，b表示接口。
具體解釋可以參照如下：
The names that begin with "usb" refer to USB controllers. More accurately, they refer to the "root hub" associated with each controller. The number is the USB bus number. In the example there is only one controller, so its bus is number 1. Hence the name "usb1".
"1-0:1.0" is a special case. It refers to the root hub's interface. This acts just like the interface in an actual hub an almost every respect; see below.
All the other entries refer to genuine USB devices and their interfaces. The devices are named by a scheme like this:
bus-port.port.port ...
In other words, the name starts with the bus number followed by a '-'. Then comes the sequence of port numbers for each of the intermediate hubs along the path to the device.
For example, "1-1" is a device plugged into bus 1, port 1. It happens to be a hub, and "1-1.3" is the device plugged into port 3 of that hub. That device is another hub, and "1-1.3.1" is the device plugged into its port 1.
The interfaces are indicated by suffixes having this form:
:config.interface
That is, a ':' followed by the configuration number followed by '.' followed by the interface number. In the above example, each of the devices is using configuration 1 and this configuration has only a single interface, number 0. So the interfaces show up as;
1-1:1.0 1-1.3:1.0 1-1.3.1:1.0
A hub will never have more than a single interface; that's part of the USB spec. But other devices can and do have multiple interfaces (and sometimes multiple configurations). Each interface gets its own entry in sysfs and can have its own driver.2、特定設備的詳細信息
進入到某個目錄中去，可以看到該設備的詳細信息，可用cat命令獲取信息。
// usb設備的詳細信息 root@ubuntu:/sys/bus/usb/devices/usb1# ll total 0 drwxr-xr-x 6 root root 0 Nov 26 21:21 ./ drwxr-xr-x 4 root root 0 Nov 26 21:21 ../ drwxr-xr-x 10 root root 0 Nov 26 21:21 1-0:1.0/ drwxr-xr-x 5 root root 0 Dec 15 23:10 1-1/ -rw-r--r-- 1 root root 4096 Dec 15 23:40 authorized -rw-r--r-- 1 root root 4096 Dec 15 23:40 authorized_default -rw-r--r-- 1 root root 4096 Dec 15 23:40 avoid_reset_quirk -r--r--r-- 1 root root 4096 Nov 26 21:21 bcdDevice -rw-r--r-- 1 root root 4096 Nov 26 21:21 bConfigurationValue -r--r--r-- 1 root root 4096 Nov 26 21:21 bDeviceClass -r--r--r-- 1 root root 4096 Nov 26 21:21 bDeviceProtocol -r--r--r-- 1 root root 4096 Nov 26 21:21 bDeviceSubClass -r--r--r-- 1 root root 4096 Dec 15 23:40 bmAttributes -r--r--r-- 1 root root 4096 Dec 15 23:40 bMaxPacketSize0 -r--r--r-- 1 root root 4096 Dec 15 23:40 bMaxPower -r--r--r-- 1 root root 4096 Dec 15 23:40 bNumConfigurations -r--r--r-- 1 root root 4096 Dec 15 23:40 bNumInterfaces -r--r--r-- 1 root root 4096 Nov 26 21:21 busnum -r--r--r-- 1 root root 4096 Dec 15 23:40 configuration -r--r--r-- 1 root root 65553 Nov 26 21:21 descriptors -r--r--r-- 1 root root 4096 Dec 15 23:40 dev -r--r--r-- 1 root root 4096 Nov 26 21:21 devnum -r--r--r-- 1 root root 4096 Dec 15 23:40 devpath lrwxrwxrwx 1 root root 0 Nov 27 20:06 driver -> ../../../../../bus/usb/drivers/usb/ drwxr-xr-x 3 root root 0 Dec 15 23:40 ep_00/ -r--r--r-- 1 root root 4096 Nov 26 21:21 idProduct -r--r--r-- 1 root root 4096 Nov 26 21:21 idVendor -r--r--r-- 1 root root 4096 Dec 15 23:40 ltm_capable -r--r--r-- 1 root root 4096 Nov 26 21:21 manufacturer -r--r--r-- 1 root root 4096 Dec 15 23:40 maxchild drwxr-xr-x 2 root root 0 Nov 26 21:21 power/ -r--r--r-- 1 root root 4096 Nov 26 21:21 product -r--r--r-- 1 root root 4096 Dec 15 23:40 quirks -r--r--r-- 1 root root 4096 Nov 26 21:21 removable --w------- 1 root root 4096 Dec 15 23:40 remove -r--r--r-- 1 root root 4096 Nov 26 21:21 serial -r--r--r-- 1 root root 4096 Nov 26 21:21 speed lrwxrwxrwx 1 root root 0 Nov 26 21:21 subsystem -> ../../../../../bus/usb/ -rw-r--r-- 1 root root 4096 Nov 26 21:21 uevent -r--r--r-- 1 root root 4096 Dec 15 23:40 urbnum -r--r--r-- 1 root root 4096 Dec 15 23:40 version
二、使用debugfs
1、掛載 debugfs 到 /sys/kernel/debug 路徑下
root@ubuntu:mount -t debugfs none /sys/kernel/debug
2、執(zhí)行上述步驟之后
在 /sys/kernel/debug 就會生成如下的文件
root@ubuntu:/sys/bus/usb/devices# cd /sys/kernel/debug/ root@ubuntu:/sys/kernel/debug# ll total 0 drwx------ 22 root root 0 Nov 26 21:21 ./ drwxr-xr-x 7 root root 0 Nov 26 21:21 ../ drwxr-xr-x 2 root root 0 Nov 26 21:21 acpi/ drwxr-xr-x 32 root root 0 Dec 4 16:30 bdi/ drwxr-xr-x 2 root root 0 Nov 26 21:21 bluetooth/ drwxr-xr-x 2 root root 0 Nov 26 21:21 cleancache/ drwxr-xr-x 2 root root 0 Nov 26 21:21 dma_buf/ drwxr-xr-x 4 root root 0 Nov 26 21:21 dri/ drwxr-xr-x 2 root root 0 Nov 26 21:21 dynamic_debug/ drwxr-xr-x 2 root root 0 Nov 26 21:21 extfrag/ drwxr-xr-x 2 root root 0 Nov 26 21:21 frontswap/ -r--r--r-- 1 root root 0 Nov 26 21:21 gpio drwxr-xr-x 3 root root 0 Nov 26 21:21 hid/ drwxr-xr-x 2 root root 0 Nov 26 21:21 kprobes/ drwxr-xr-x 3 root root 0 Nov 26 21:21 kvm-guest/ drwxr-xr-x 2 root root 0 Nov 26 21:21 mce/ drwxr-xr-x 2 root root 0 Nov 26 21:21 pinctrl/ -r--r--r-- 1 root root 0 Nov 26 21:21 pwm drwxr-xr-x 2 root root 0 Nov 26 21:21 regmap/ drwxr-xr-x 3 root root 0 Nov 26 21:21 regulator/ -rw-r--r-- 1 root root 0 Nov 26 21:21 sched_features -r--r--r-- 1 root root 0 Nov 26 21:21 sleep_time -r--r--r-- 1 root root 0 Nov 26 21:21 suspend_stats drwxr-xr-x 7 root root 0 Nov 26 21:21 tracing/ drwxr-xr-x 3 root root 0 Nov 26 21:21 usb/ drwxr-xr-x 2 root root 0 Nov 26 21:21 virtio-ports/ -r--r--r-- 1 root root 0 Nov 26 21:21 vmmemctl -r--r--r-- 1 root root 0 Nov 26 21:21 wakeup_sources drwxr-xr-x 2 root root 0 Nov 26 21:21 x86/
3、cat 設備節(jié)點
執(zhí)行下述命令之后會以特定格式打印目前USB總線上所有USB設備的信息如下：
root@ubuntu:/sys/kernel/debug# cat usb/devices T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 17/900 us ( 2%), #Int= 1, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 3.13 S: Manufacturer=Linux 3.13.0-32-generic uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=0000:02:00.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0e0f ProdID=0003 Rev= 1.03 S: Manufacturer=VMware S: Product=VMware Virtual USB Mouse C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=1ms T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 7 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0e0f ProdID=0002 Rev= 1.00 S: Product=VMware Virtual USB Hub C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 B: Alloc= 0/800 us ( 0%), #Int= 1, #Iso= 0 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev= 3.13 S: Manufacturer=Linux 3.13.0-32-generic ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=0000:02:03.0 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 7 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=0129 Rev=39.60 S: Manufacturer=Generic S: Product=USB2.0-CRW S: SerialNumber=20100201396000000 C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=06 Prot=50 Driver=rts5139 E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 3 Ivl=64ms
至于信息的詳細解析可以參照 Linux源代碼中 Documentation/usb/proc_usb_info.txt 文件。
現(xiàn)摘錄其中對該格式的詳細解釋：
Each line is tagged with a one-character ID for that line:
T = Topology (etc.)
B = Bandwidth (applies only to USB host controllers, which are
virtualized as root hubs)
D = Device descriptor info.
P = Product ID info. (from Device descriptor, but they won't fit
together on one line)
S = String descriptors.
C = Configuration descriptor info. (* = active configuration)
I = Interface descriptor info.
E = Endpoint descriptor info.
Legend:
d = decimal number (may have leading spaces or 0's)
x = hexadecimal number (may have leading spaces or 0's)
s = string
Topology info:
T: Bus=dd Lev=dd Prnt=dd Port=dd Cnt=dd Dev#=ddd Spd=dddd MxCh=dd
| | | | | | | | |__MaxChildren
| | | | | | | |__Device Speed in Mbps
| | | | | | |__DeviceNumber
| | | | | |__Count of devices at this level
| | | | |__Connector/Port on Parent for this device
| | | |__Parent DeviceNumber
| | |__Level in topology for this bus
| |__Bus number
|__Topology info tag
Speed may be:
1.5 Mbit/s for low speed USB
12 Mbit/s for full speed USB
480 Mbit/s for high speed USB (added for USB 2.0);
also used for Wireless USB, which has no fixed speed
5000 Mbit/s for SuperSpeed USB (added for USB 3.0)
For reasons lost in the mists of time, the Port number is always
too low by 1. For example, a device plugged into port 4 will
show up with "Port=03".
Bandwidth info:
B: Alloc=ddd/ddd us (xx%), #Int=ddd, #Iso=ddd
| | | |__Number of isochronous requests
| | |__Number of interrupt requests
| |__Total Bandwidth allocated to this bus
|__Bandwidth info tag
Bandwidth allocation is an approximation of how much of one frame
(millisecond) is in use. It reflects only periodic transfers, which
are the only transfers that reserve bandwidth. Control and bulk
transfers use all other bandwidth, including reserved bandwidth that
is not used for transfers (such as for short packets).
The percentage is how much of the "reserved" bandwidth is scheduled by
those transfers. For a low or full speed bus (loosely, "USB 1.1"),
90% of the bus bandwidth is reserved. For a high speed bus (loosely,
"USB 2.0") 80% is reserved.
Device descriptor info & Product ID info:
D: Ver=x.xx Cls=xx(s) Sub=xx Prot=xx MxPS=dd #Cfgs=dd
P: Vendor=xxxx ProdID=xxxx Rev=xx.xx
where
D: Ver=x.xx Cls=xx(sssss) Sub=xx Prot=xx MxPS=dd #Cfgs=dd
| | | | | | |__NumberConfigurations
| | | | | |__MaxPacketSize of Default Endpoint
| | | | |__DeviceProtocol
| | | |__DeviceSubClass
| | |__DeviceClass
| |__Device USB version
|__Device info tag #1
where
P: Vendor=xxxx ProdID=xxxx Rev=xx.xx
| | | |__Product revision number
| | |__Product ID code
| |__Vendor ID code
|__Device info tag #2
String descriptor info:
S: Manufacturer=ssss
| |__Manufacturer of this device as read from the device.
| For USB host controller drivers (virtual root hubs) this may
| be omitted, or (for newer drivers) will identify the kernel
| version and the driver which provides this hub emulation.
|__String info tag
S: Product=ssss
| |__Product description of this device as read from the device.
| For older USB host controller drivers (virtual root hubs) this
| indicates the driver; for newer ones, it's a product (and vendor)
| description that often comes from the kernel's PCI ID database.
|__String info tag
S: SerialNumber=ssss
| |__Serial Number of this device as read from the device.
| For USB host controller drivers (virtual root hubs) this is
| some unique ID, normally a bus ID (address or slot name) that
| can't be shared with any other device.
|__String info tag
Configuration descriptor info:
C:* #Ifs=dd Cfg#=dd Atr=xx MPwr=dddmA
| | | | | |__MaxPower in mA
| | | | |__Attributes
| | | |__ConfiguratioNumber
| | |__NumberOfInterfaces
| |__ "*" indicates the active configuration (others are " ")
|__Config info tag
USB devices may have multiple configurations, each of which act
rather differently. For example, a bus-powered configuration
might be much less capable than one that is self-powered. Only
one device configuration can be active at a time; most devices
have only one configuration.
Each configuration consists of one or more interfaces. Each
interface serves a distinct "function", which is typically bound
to a different USB device driver. One common example is a USB
speaker with an audio interface for playback, and a HID interface
for use with software volume control.
Interface descriptor info (can be multiple per Config):
I:* If#=dd Alt=dd #EPs=dd Cls=xx(sssss) Sub=xx Prot=xx Driver=ssss
| | | | | | | | |__Driver name
| | | | | | | | or "(none)"
| | | | | | | |__InterfaceProtocol
| | | | | | |__InterfaceSubClass
| | | | | |__InterfaceClass
| | | | |__NumberOfEndpoints
| | | |__AlternateSettingNumber
| | |__InterfaceNumber
| |__ "*" indicates the active altsetting (others are " ")
|__Interface info tag
A given interface may have one or more "alternate" settings.
For example, default settings may not use more than a small
amount of periodic bandwidth. To use significant fractions
of bus bandwidth, drivers must select a non-default altsetting.
Only one setting for an interface may be active at a time, and
only one driver may bind to an interface at a time. Most devices
have only one alternate setting per interface.
Endpoint descriptor info (can be multiple per Interface):
E: Ad=xx(s) Atr=xx(ssss) MxPS=dddd Ivl=dddss
| | | | |__Interval (max) between transfers
| | | |__EndpointMaxPacketSize
| | |__Attributes(EndpointType)
| |__EndpointAddress(I=In,O=Out)
|__Endpoint info tag
The interval is nonzero for all periodic (interrupt or isochronous)
endpoints. For high speed endpoints the transfer interval may be
measured in microseconds rather than milliseconds.
For high speed periodic endpoints, the "MaxPacketSize" reflects
the per-microframe data transfer size. For "high bandwidth"
endpoints, that can reflect two or three packets (for up to
3KBytes every 125 usec) per endpoint.
With the Linux-USB stack, periodic bandwidth reservations use the
transfer intervals and sizes provided by URBs, which can be less
than those found in endpoint descriptor.總結
以上為個人經驗，希望能給大家一個參考，也希望大家多多支持腳本之家。
相關文章
火山互聯(lián)推出的免費VPS...拿來學習下還是不錯的.申請過幾次Liunx系統(tǒng)的.由于不是很熟悉.幾次都沒能配置好.下面介紹一下.前幾天又申請了一個.2009-12-12
linux下統(tǒng)計appche站點IP訪問量的shell腳本
這篇文章主要介紹了linux下統(tǒng)計appche站點IP訪問量的幾種shell腳本以及執(zhí)行結果2014-06-06
在Linux操作系統(tǒng)中,內存管理是確保系統(tǒng)性能和穩(wěn)定性的核心組成部分,對于開發(fā)者來說,理解內存分配機制不僅有助于編寫更高效的程序,還能幫助他們更好地調試和優(yōu)化應用,本文給大家介紹了Linux如何進行內存分配,需要的朋友可以參考下2025-02-02
Kafka是一個分布式的、可分區(qū)的、可復制的消息系統(tǒng)。它提供了普通消息系統(tǒng)的功能，但具有自己獨特的設計。這個獨特的設計是什么樣的呢2015-12-12
YUM解決RPM包安裝依賴關系及yum工具介紹本地源配置方法詳解
這篇文章主要介紹了YUM解決RPM包安裝依賴關系及yum工具介紹本地源配置方法詳解,本文給大家介紹的非常詳細具有參考借鑒價值，需要的朋友可以參考下2016-10-10
在Linux上一直使用vim，慢慢熟悉了它的命令，才終于領悟了什么是編輯器之神。最近抽空整理了這份速查表，感興趣的朋友跟隨小編一起看看吧2018-10-10
CentOS7開啟MySQL8主從備份、每日定時全量備份(推薦)
這篇文章主要介紹了CentOS7開啟MySQL8主從備份、每日定時全量備份,解決了鏈接mysql數據庫很慢的問題，非常不錯，具有一定的參考借鑒價值，需要的朋友可以參考下2019-11-11
在 RHEL8 /CentOS8 上建立多節(jié)點 Elastic stack 集群的方法
Elastic stack 俗稱 ELK stack，是一組包括 Elasticsearch、Logstash 和 Kibana 在內的開源產品。Elastic Stack 由 Elastic 公司開發(fā)和維護。這篇文章主要介紹了如何在 RHEL8 /CentOS8 上建立多節(jié)點 Elastic stack 集群,需要的朋友可以參考下2019-09-09
Ubuntu16.04 靜態(tài)IP地址設置（NAT方式）
這篇文章主要介紹了Ubuntu16.04 靜態(tài)IP地址設置（NAT方式），詳細的介紹了為VMware虛擬機內安裝的Ubuntu 16.04設置靜態(tài)IP地址NAT方式，有興趣的可以了解一下。2017-02-02
本篇文章主要介紹了centos7中firewall防火墻命令詳解，具有一定的參考價值，有需要的可以了解一下。2016-11-11