From: Oliver Neukum <oneukum@suse.com>
To: "Tomasz Moń" <tomasz.mon@nordicsemi.no>,
"Andreas Noever" <andreas.noever@gmail.com>,
"Michael Jamet" <michael.jamet@intel.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Yehezkel Bernat" <YehezkelShB@gmail.com>,
linux-usb@vger.kernel.org
Subject: Re: USB 2.0 host controller for Thunderbolt 4
Date: Tue, 23 May 2023 11:44:34 +0200 [thread overview]
Message-ID: <0dc2e12d-052f-aa59-07df-5158b924ec12@suse.com> (raw)
In-Reply-To: <bd807b391dec726401e36a25f8c8987571d771be.camel@nordicsemi.no>
On 23.05.23 10:53, Tomasz Moń wrote:
> Hello,
>
> Dell Latitude 5330 with 12th Gen Intel(R) Core(TM) i7-1265U contains
> following PCI devices:
> * 8086:461e - Alder Lake-P Thunderbolt 4 USB Controller
> * 8086:51ed - Alder Lake PCH USB 3.2 xHCI Host Controller
>
> Thunderbolt 4 USB Controller initializes first and therefore following
> usb host controllers are registered:
> * usb1 - USB 2.0 High-Speed
> * usb2 - USB 3.2 Enhanced SuperSpeed
> * usb3 - USB 2.0 High-Speed
> * usb4 - USB 3.1 Enhanced SuperSpeed
>
> When I connect SuperSpeed device directly to the Dell Latitude, it ends
> up on usb4. Low/Full/High-Speed devices end up on usb3 as expected.
>
> When I connect Thunderbolt 3 dock, two new host controllers show up:
> * usb5 - USB 2.0 High-Speed
> * usb6 - USB 3.0 SuperSpeed
Could you provide lspci in that state?
AFAICT there is nothing that would prevent a vendor from putting
a PCI HC into a TB3 docking station.
Regards
Oliver
next prev parent reply other threads:[~2023-05-23 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 8:53 USB 2.0 host controller for Thunderbolt 4 Tomasz Moń
2023-05-23 9:01 ` Mika Westerberg
2023-05-23 9:45 ` Moń, Tomasz
2023-05-23 11:03 ` Mathias Nyman
2023-05-23 12:54 ` mika.westerberg
2023-05-23 9:44 ` Oliver Neukum [this message]
2023-05-23 9:49 ` Tomasz Moń
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=0dc2e12d-052f-aa59-07df-5158b924ec12@suse.com \
--to=oneukum@suse.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=tomasz.mon@nordicsemi.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox