public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Gil Fine <gil.fine@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 00/12] thunderbolt: Improvements to XDomain handling
Date: Mon, 27 Apr 2026 10:10:57 +0200	[thread overview]
Message-ID: <20260427081109.2337731-1-mika.westerberg@linux.intel.com> (raw)

Hi all,

This series improves the Thunderbolt peer-to-peer (aka XDomain) handling in
various places in the driver and tries to make it follow the USB4 spec more
closely.

Alan Borzeszkowski (1):
  thunderbolt: Don't create multiple DMA tunnels on firmware connection manager

Gil Fine (1):
  thunderbolt: Avoid reserved fields in path config space for USB4 routers

Mika Westerberg (10):
  thunderbolt: Don't disable lane adapter if XDomain lane bonding isn't possible
  thunderbolt: Make XDomain lane bonding comply with the USB4 v2 spec
  thunderbolt: Keep the domain reference while processing hotplug
  thunderbolt: Release request if tb_cfg_request() fails in __tb_xdomain_response()
  thunderbolt: Set tb->root_switch to NULL when domain is stopped
  thunderbolt: Wait for tb_domain_release() to complete when driver is removed
  thunderbolt: Keep XDomain reference during the lifetime of a service
  thunderbolt: dma_test: No need to store debugfs directory pointer
  thunderbolt: Remove service debugfs entries during unregister
  thunderbolt: Remove XDomain from the bus without holding tb->lock

 drivers/thunderbolt/debugfs.c  |   2 +
 drivers/thunderbolt/dma_test.c |  20 ++--
 drivers/thunderbolt/domain.c   |  33 ++++++
 drivers/thunderbolt/icm.c      |  15 +++
 drivers/thunderbolt/nhi.c      |   4 +
 drivers/thunderbolt/path.c     |  31 ++++--
 drivers/thunderbolt/switch.c   |  14 +++
 drivers/thunderbolt/tb.c       |  65 ++++++------
 drivers/thunderbolt/tb.h       |   2 +
 drivers/thunderbolt/xdomain.c  | 181 +++++++++++++++++++++++----------
 include/linux/thunderbolt.h    |   4 +
 11 files changed, 269 insertions(+), 102 deletions(-)

-- 
2.50.1


             reply	other threads:[~2026-04-27  8:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27  8:10 Mika Westerberg [this message]
2026-04-27  8:10 ` [PATCH 01/12] thunderbolt: Avoid reserved fields in path config space for USB4 routers Mika Westerberg
2026-04-27  8:10 ` [PATCH 02/12] thunderbolt: Don't disable lane adapter if XDomain lane bonding isn't possible Mika Westerberg
2026-04-27  8:11 ` [PATCH 03/12] thunderbolt: Make XDomain lane bonding comply with the USB4 v2 spec Mika Westerberg
2026-04-27  8:11 ` [PATCH 04/12] thunderbolt: Keep the domain reference while processing hotplug Mika Westerberg
2026-04-27  8:11 ` [PATCH 05/12] thunderbolt: Release request if tb_cfg_request() fails in __tb_xdomain_response() Mika Westerberg
2026-04-27  8:11 ` [PATCH 06/12] thunderbolt: Set tb->root_switch to NULL when domain is stopped Mika Westerberg
2026-04-27  8:11 ` [PATCH 07/12] thunderbolt: Wait for tb_domain_release() to complete when driver is removed Mika Westerberg
2026-04-27  8:11 ` [PATCH 08/12] thunderbolt: Keep XDomain reference during the lifetime of a service Mika Westerberg
2026-04-27  8:11 ` [PATCH 09/12] thunderbolt: dma_test: No need to store debugfs directory pointer Mika Westerberg
2026-04-27  8:11 ` [PATCH 10/12] thunderbolt: Remove service debugfs entries during unregister Mika Westerberg
2026-04-27  8:11 ` [PATCH 11/12] thunderbolt: Remove XDomain from the bus without holding tb->lock Mika Westerberg
2026-04-27  8:11 ` [PATCH 12/12] thunderbolt: Don't create multiple DMA tunnels on firmware connection manager 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=20260427081109.2337731-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 \
    /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