All of lore.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>,
	Michael Jamet <michael.jamet@intel.com>,
	Andreas Noever <andreas.noever@gmail.com>,
	Lukas Wunner <lukas@wunner.de>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 0/5] thunderbolt: Add support for XDomain lane bonding
Date: Tue, 26 Apr 2022 14:25:35 +0300	[thread overview]
Message-ID: <20220426112540.6053-1-mika.westerberg@linux.intel.com> (raw)

Hi all,

So far connecting two Thunderbolt/USB4 domains (hosts) the high-speed link
has been using a single lane. The reason for this was simplicity and also
the fact that the host DMA was not able to go over the 20 Gbit/s even if
the lanes were bonded. However, Intel Alder Lake and beyond actually can go
higher than that so now it makes more sense to take advantage of the lane
bonding. The USB4 Inter-Domain Service specification describes the
protocol and this patch series implements it for the Linux Thunderbolt/USB4
driver.

If both sides (hosts) of the link announce supporting this, we will
establish bonded link. This is only possible on systems with software based
connection manager (so Intel Alder Lake and beyond).

Mika Westerberg (5):
  thunderbolt: Add debug logging when lane is enabled/disabled
  thunderbolt: Move tb_port_state() prototype to correct place
  thunderbolt: Split setting link width and lane bonding into own functions
  thunderbolt: Ignore port locked error in tb_port_wait_for_link_width()
  thunderbolt: Add support for XDomain lane bonding

 drivers/thunderbolt/switch.c  | 109 ++++--
 drivers/thunderbolt/tb.c      |   6 -
 drivers/thunderbolt/tb.h      |   4 +-
 drivers/thunderbolt/tb_msgs.h |  39 +++
 drivers/thunderbolt/tb_regs.h |   5 +
 drivers/thunderbolt/xdomain.c | 609 ++++++++++++++++++++++++++++++----
 include/linux/thunderbolt.h   |  19 +-
 7 files changed, 688 insertions(+), 103 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-04-26 11:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 11:25 Mika Westerberg [this message]
2022-04-26 11:25 ` [PATCH 1/5] thunderbolt: Add debug logging when lane is enabled/disabled Mika Westerberg
2022-04-26 11:25 ` [PATCH 2/5] thunderbolt: Move tb_port_state() prototype to correct place Mika Westerberg
2022-04-26 11:25 ` [PATCH 3/5] thunderbolt: Split setting link width and lane bonding into own functions Mika Westerberg
2022-04-26 11:25 ` [PATCH 4/5] thunderbolt: Ignore port locked error in tb_port_wait_for_link_width() Mika Westerberg
2022-04-26 11:25 ` [PATCH 5/5] thunderbolt: Add support for XDomain lane bonding Mika Westerberg
2022-05-05  6:29 ` [PATCH 0/5] " 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=20220426112540.6053-1-mika.westerberg@linux.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=michael.jamet@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.