From: Greg KH <gregkh@linuxfoundation.org>
To: Douglas Gilbert <dgilbert@interlog.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: device present in lsusb, disappears in lsusb -t
Date: Sat, 16 Sep 2023 13:16:17 +0200 [thread overview]
Message-ID: <2023091638-duration-barcode-73a3@gregkh> (raw)
In-Reply-To: <70c563f1-847c-32a1-cf4d-6bf9802017ab@interlog.com>
On Fri, Sep 15, 2023 at 08:16:18PM -0400, Douglas Gilbert wrote:
> The device in question is this one:
> Bus 005 Device 015: ID 0483:572b STMicroelectronics STEVAL-USBC2DP Type-C
> to DisplayPort adapter. It is a USB-C alternate mode device (so tbtadm does
> not
> report it).
>
> That adapter is connected to a screen (and working) and to a USB-C port on
> a Lenovo TB3 dock [40AN] which in turn is connected to a Thinkpad X13 Gen3's
> USB-C port. The Thinkpad is running lk 6.6.0-rc1 with "lsusb (usbutils) 014".
>
> The strange thing is that this device is nowhere to be found in the output
> of "lsusb -t". The lsusb manpage describes the '-t' option as: "Tells
> lsusb to dump the physical USB device hierarchy as a tree." So is 'physical'
> a weasel word in this context, or is there a bug in the '-t' option, or is
> there some other explanation?
A number of 'lsusb -t' issues were fixed in the 015 release of usbutils,
so maybe update?
that being said, the -t option is a totally different codepath in the
tool, and shows different things overall. -t shows the drivers that are
bound to the different interfaces, which means that a single device will
show up multiple times in the -t option.
Here's the output of the two things on my local laptop, with just a few
USB devices in it:
$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 003 Device 006: ID 0bda:5634 Realtek Semiconductor Corp. Laptop Camera
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 7: Dev 6, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 7: Dev 6, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 10: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 10: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 20000M/x2
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
and then if you give the -v option as well you see a bit more:
$ lsusb -tv
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 7: Dev 6, If 0, Class=Video, Driver=uvcvideo, 480M
ID 0bda:5634 Realtek Semiconductor Corp.
|__ Port 7: Dev 6, If 1, Class=Video, Driver=uvcvideo, 480M
ID 0bda:5634 Realtek Semiconductor Corp.
|__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd.
|__ Port 10: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
ID 8087:0032 Intel Corp. AX210 Bluetooth
|__ Port 10: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M
ID 8087:0032 Intel Corp. AX210 Bluetooth
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 20000M/x2
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
What are you seeing missing in your output?
thanks,
greg k-h
next prev parent reply other threads:[~2023-09-16 11:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 0:16 device present in lsusb, disappears in lsusb -t Douglas Gilbert
2023-09-16 11:16 ` Greg KH [this message]
2023-10-06 2:49 ` Douglas Gilbert
2023-10-11 9:30 ` Greg KH
2023-10-11 15:00 ` Alan Stern
2023-10-11 18:51 ` Douglas Gilbert
2023-10-12 12:50 ` Greg KH
2023-10-12 14:38 ` Douglas Gilbert
2023-10-12 19:10 ` Alan Stern
2023-10-13 2:12 ` Douglas Gilbert
2023-10-13 14:50 ` Alan Stern
2023-10-13 21:44 ` Douglas Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2023091638-duration-barcode-73a3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dgilbert@interlog.com \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.