From: Greg KH <gregkh@linuxfoundation.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Mario Limonciello <superm1@kernel.org>,
"Rangoju, Raju" <raju.rangoju@amd.com>,
linux-usb@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, andreas.noever@gmail.com,
michael.jamet@intel.com, westeri@kernel.org,
YehezkelShB@gmail.com, bhelgaas@google.com, Sanath.S@amd.com
Subject: Re: [PATCH 0/3] thunderbolt: Update XDomain vendor properties dynamically
Date: Wed, 13 Aug 2025 17:26:31 +0200 [thread overview]
Message-ID: <2025081320-payroll-skydiver-51e5@gregkh> (raw)
In-Reply-To: <20250811052555.GQ476609@black.igk.intel.com>
On Mon, Aug 11, 2025 at 07:25:55AM +0200, Mika Westerberg wrote:
> On Mon, Aug 11, 2025 at 06:53:07AM +0200, Mika Westerberg wrote:
> > On Fri, Aug 08, 2025 at 04:13:28PM +0100, Greg KH wrote:
> > > > 0004 USB4
> > > >
> > > > sounds good to me. In USB4 there is no "root hub". It's called host router
> > > > (but we do have device routers that are called USB4 hubs for added
> > > > confusion ;-).
> > > >
> > > > But I'm fine with other numbers too, does not matter if you want to save it
> > > > for some future USB variant.
> > >
> > > Ok, use 0004 for this. But what should I use for the text string here
> > > in the usb.ids file?
> >
> > Thanks! I'll cook up a patch changing these.
> >
> > I don't think it should be in usb.ids because it is not visible anywhere
> > except over USB4 link (between hosts). You don't see this through USB 2.x
> > or 3.x.
>
> Of course for documentation purposes it could be:
>
> 0004 Linux USB4 Connection Manager
>
Now updated, thanks!
greg k-h
next prev parent reply other threads:[~2025-08-13 15:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 17:50 [PATCH 0/3] thunderbolt: Update XDomain vendor properties dynamically Raju Rangoju
2025-07-22 17:50 ` [PATCH 1/3] thunderbolt: Dynamically populate vendor properties for XDomain Raju Rangoju
2025-07-22 17:50 ` [PATCH 2/3] PCI: Add PCI vendor ID for ASMedia USB4 devices Raju Rangoju
2025-07-22 19:14 ` Bjorn Helgaas
2025-07-23 10:16 ` Rangoju, Raju
2025-07-22 17:50 ` [PATCH 3/3] thunderbolt: Add vendor ASMedia in update_property_block for XDomain Raju Rangoju
2025-07-28 6:47 ` [PATCH 0/3] thunderbolt: Update XDomain vendor properties dynamically Mika Westerberg
2025-08-06 6:16 ` Rangoju, Raju
2025-08-06 8:51 ` Mika Westerberg
2025-08-06 14:06 ` Mario Limonciello
2025-08-06 15:00 ` Mika Westerberg
2025-08-06 15:05 ` Mario Limonciello
2025-08-06 16:58 ` Greg KH
2025-08-07 5:15 ` Mika Westerberg
2025-08-07 16:02 ` Greg KH
2025-08-07 16:07 ` Mario Limonciello
2025-08-08 4:45 ` Mika Westerberg
2025-08-08 9:02 ` Greg KH
2025-08-08 9:13 ` Mika Westerberg
2025-08-08 15:13 ` Greg KH
2025-08-11 4:53 ` Mika Westerberg
2025-08-11 5:25 ` Mika Westerberg
2025-08-13 15:26 ` Greg KH [this message]
2025-08-11 5:28 ` Greg KH
2025-08-11 7:02 ` Mika Westerberg
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=2025081320-payroll-skydiver-51e5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Sanath.S@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=raju.rangoju@amd.com \
--cc=superm1@kernel.org \
--cc=westeri@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox