From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-usb@vger.kernel.org
Cc: Yehezkel Bernat <YehezkelShB@gmail.com>,
Lukas Wunner <lukas@wunner.de>,
Andreas Noever <andreas.noever@gmail.com>,
Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>,
Pooja Katiyar <pooja.katiyar@intel.com>,
Rene Sapiens <rene.sapiens@linux.intel.com>,
Gil Fine <gil.fine@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 0/8] thunderbolt: Make the driver follow CM guide more closely
Date: Tue, 12 May 2026 14:29:47 +0200 [thread overview]
Message-ID: <20260512122955.271688-1-mika.westerberg@linux.intel.com> (raw)
Hi all,
This series includes various improvements to make the Thunderbolt/USB4
driver follow the USB4 Connection Manager guide more closely (and hopefully
work better with wider range of USB4 devices). There is also one
improvement for DisplayPort tunneling with more than 2 tunnels when
bandwidth allocation mode is enabled.
Alan Borzeszkowski (1):
thunderbolt: Improve multi-display DisplayPort tunnel allocation
Gil Fine (6):
thunderbolt: Fix lane bonding log when bonding not possible
thunderbolt: Activate path hops from source to destination
thunderbolt: Verify PCIe adapter in detect state before tunnel setup
thunderbolt: Verify Router Ready bit is set after router enumeration
thunderbolt: Increase timeout for Configuration Ready bit
thunderbolt: Increase Notification Timeout to 255 ms for USB4 routers
Pooja Katiyar (1):
thunderbolt: Don't access path config space on Lane 1 adapters in tb_switch_reset_host()
drivers/thunderbolt/path.c | 6 +++---
drivers/thunderbolt/switch.c | 22 +++++++++++-----------
drivers/thunderbolt/tb.c | 3 +++
drivers/thunderbolt/tb.h | 1 +
drivers/thunderbolt/tb_regs.h | 19 +++++++++++++++++--
drivers/thunderbolt/tunnel.c | 35 +++++++++++++++++++++++++++++++++++
drivers/thunderbolt/usb4.c | 35 ++++++++++++++++++++++++++++++++---
7 files changed, 102 insertions(+), 19 deletions(-)
--
2.50.1
next reply other threads:[~2026-05-12 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 12:29 Mika Westerberg [this message]
2026-05-12 12:29 ` [PATCH 1/8] thunderbolt: Improve multi-display DisplayPort tunnel allocation Mika Westerberg
2026-05-12 12:29 ` [PATCH 2/8] thunderbolt: Don't access path config space on Lane 1 adapters in tb_switch_reset_host() Mika Westerberg
2026-05-12 12:29 ` [PATCH 3/8] thunderbolt: Fix lane bonding log when bonding not possible Mika Westerberg
2026-05-12 12:29 ` [PATCH 4/8] thunderbolt: Activate path hops from source to destination Mika Westerberg
2026-05-12 12:29 ` [PATCH 5/8] thunderbolt: Verify PCIe adapter in detect state before tunnel setup Mika Westerberg
2026-05-12 12:29 ` [PATCH 6/8] thunderbolt: Verify Router Ready bit is set after router enumeration Mika Westerberg
2026-05-12 12:29 ` [PATCH 7/8] thunderbolt: Increase timeout for Configuration Ready bit Mika Westerberg
2026-05-12 12:29 ` [PATCH 8/8] thunderbolt: Increase Notification Timeout to 255 ms for USB4 routers 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=20260512122955.271688-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=alan.borzeszkowski@linux.intel.com \
--cc=andreas.noever@gmail.com \
--cc=gil.fine@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=pooja.katiyar@intel.com \
--cc=rene.sapiens@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox