From: Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>
To: linux-usb@vger.kernel.org
Cc: mika.westerberg@linux.intel.com, andreas.noever@gmail.com,
michael.jamet@intel.com, YehezkelShB@gmail.com,
heikki.krogerus@linux.intel.com, gregkh@linuxfoundation.org
Subject: [PATCH 0/3] Introduce Thunderbolt/USB4 <-> USB Type-C port mapping
Date: Mon, 14 Apr 2025 19:55:51 +0200 [thread overview]
Message-ID: <20250414175554.107228-1-alan.borzeszkowski@linux.intel.com> (raw)
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.
Alan Borzeszkowski (3):
thunderbolt: Expose usb4_port_index() to other modules
thunderbolt: Add Thunderbolt/USB4 <-> USB3 match function
usb: typec: Connect Type-C port with associated USB4 port
drivers/thunderbolt/tb.h | 1 +
drivers/thunderbolt/usb4.c | 14 +++++++--
drivers/thunderbolt/usb4_port.c | 56 ++++++++++++++++++++++++++++-----
drivers/usb/typec/port-mapper.c | 23 ++++++++++++--
include/linux/thunderbolt.h | 18 +++++++++++
5 files changed, 99 insertions(+), 13 deletions(-)
base-commit: 306a14d03f47fa152c7e47be544d8d582d387a20
--
2.43.0
next reply other threads:[~2025-04-14 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 17:55 Alan Borzeszkowski [this message]
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
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=20250414175554.107228-1-alan.borzeszkowski@linux.intel.com \
--to=alan.borzeszkowski@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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.