From: Greg KH <gregkh@linuxfoundation.org>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>,
linux-usb@vger.kernel.org, mika.westerberg@linux.intel.com,
andreas.noever@gmail.com, michael.jamet@intel.com,
YehezkelShB@gmail.com
Subject: Re: [PATCH 0/3] Introduce Thunderbolt/USB4 <-> USB Type-C port mapping
Date: Tue, 15 Apr 2025 14:22:10 +0200 [thread overview]
Message-ID: <2025041557-jot-compel-75ec@gregkh> (raw)
In-Reply-To: <Z_4nm3x6TvgkO4Rl@kuha.fi.intel.com>
On Tue, Apr 15, 2025 at 12:32:11PM +0300, Heikki Krogerus wrote:
> Hi Greg,
>
> On Mon, Apr 14, 2025 at 09:03:42PM +0200, Greg KH wrote:
> > On Mon, Apr 14, 2025 at 07:55:51PM +0200, Alan Borzeszkowski wrote:
> > > Hello everyone,
> > >
> > > This patch series introduces the creation of symlinks between
> > > Thunderbolt/USB4 ports and their corresponding USB Type-C ports. The
> > > primary goal is to provide users with clear visibility into which USB4
> > > port is connected via a specific Type-C port. This provides the same
> > > functionality that is already present in Chromebooks.
> >
> > "mapping" in what way? sysfs links? If so, care to add
> > Documentation/ABI/ updates?
>
> It is already there:
> https://docs.kernel.org/admin-guide/abi-testing.html#abi-sys-bus-thunderbolt-devices-usb4-portx-connector
>
> The link is already created on Cromebooks like Alan explained, because
> there each USB4/TBT port has a device node in the ACPI tables with the
> appropriate _PLD (Physical Location of Device), but on systems
> targeted primarily for Windows, that is not the case. There ports do
> not have device nodes, so we can't make the link based on _PLD.
>
> This series makes that same link by taking advantage of the
> "usb4-host-interface" _DSD device property [1] that we always have on
> those Windows platforms. That same device property that we also use in
> drivers/usb/code/usb-acpi.c, and probable some other places too.
>
> [1] https://www.usb.org/sites/default/files/D1T2-2%20-%20USB4%20on%20Windows.pdf
Thanks for the information, sorry I had missed that it was already
there.
greg k-h
next prev parent reply other threads:[~2025-04-15 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 17:55 [PATCH 0/3] Introduce Thunderbolt/USB4 <-> USB Type-C port mapping Alan Borzeszkowski
2025-04-14 17:55 ` [PATCH 1/3] thunderbolt: Expose usb4_port_index() to other modules Alan Borzeszkowski
2025-04-14 17:55 ` [PATCH 2/3] thunderbolt: Add Thunderbolt/USB4 <-> USB3 match function Alan Borzeszkowski
2025-04-14 17:55 ` [PATCH 3/3] usb: typec: Connect Type-C port with associated USB4 port Alan Borzeszkowski
2025-04-14 19:03 ` [PATCH 0/3] Introduce Thunderbolt/USB4 <-> USB Type-C port mapping Greg KH
2025-04-15 9:32 ` Heikki Krogerus
2025-04-15 12:22 ` Greg KH [this message]
2025-04-15 12:22 ` Greg KH
2025-04-15 12:36 ` Mika Westerberg
2025-04-17 9:27 ` 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=2025041557-jot-compel-75ec@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=YehezkelShB@gmail.com \
--cc=alan.borzeszkowski@linux.intel.com \
--cc=andreas.noever@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
/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.