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>,
Lukas Wunner <lukas@wunner.de>,
Andreas Noever <andreas.noever@gmail.com>,
Gil Fine <gil.fine@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 00/10] thunderbolt: USB4 v2 asymmetric switching and more
Date: Thu, 5 Oct 2023 12:27:19 +0300 [thread overview]
Message-ID: <20231005092729.3595447-1-mika.westerberg@linux.intel.com> (raw)
Hi all,
This series adds more USB4 v2 features. First it makes the bandwidth
reservation to comply with the v2 connection manager guide, adds the
PMPS packet support bit and enables asymmetric 120/40G switching to
support the Ultra-High Bitrate DisplayPort modes.
Applies on top of the cleanup series I sent out this week [1].
[1] https://lore.kernel.org/linux-usb/20231003094005.2676823-1-mika.westerberg@linux.intel.com/
Gil Fine (5):
thunderbolt: Make is_gen4_link() available to the rest of the driver
thunderbolt: Change bandwidth reservations to comply USB4 v2
thunderbolt: Introduce tb_port_path_direction_downstream()
thunderbolt: Add support for asymmetric link
thunderbolt: Configure asymmetric link if needed and bandwidth allows
Mika Westerberg (5):
thunderbolt: Use constants for path weight and priority
thunderbolt: Use weight constants in tb_usb3_consumed_bandwidth()
thunderbolt: Set path power management packet support bit for USB4 v2 routers
thunderbolt: Introduce tb_for_each_upstream_port_on_path()
thunderbolt: Introduce tb_switch_depth()
drivers/thunderbolt/path.c | 7 +-
drivers/thunderbolt/switch.c | 328 +++++++++++++---
drivers/thunderbolt/tb.c | 682 ++++++++++++++++++++++++++++------
drivers/thunderbolt/tb.h | 58 ++-
drivers/thunderbolt/tb_regs.h | 12 +-
drivers/thunderbolt/tunnel.c | 161 ++++++--
drivers/thunderbolt/tunnel.h | 2 +
drivers/thunderbolt/usb4.c | 106 ++++++
8 files changed, 1142 insertions(+), 214 deletions(-)
--
2.40.1
next reply other threads:[~2023-10-05 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 9:27 Mika Westerberg [this message]
2023-10-05 9:27 ` [PATCH 01/10] thunderbolt: Use constants for path weight and priority Mika Westerberg
2023-10-05 9:27 ` [PATCH 02/10] thunderbolt: Use weight constants in tb_usb3_consumed_bandwidth() Mika Westerberg
2023-10-05 9:27 ` [PATCH 03/10] thunderbolt: Make is_gen4_link() available to the rest of the driver Mika Westerberg
2023-10-05 9:27 ` [PATCH 04/10] thunderbolt: Change bandwidth reservations to comply USB4 v2 Mika Westerberg
2023-10-05 9:27 ` [PATCH 05/10] thunderbolt: Set path power management packet support bit for USB4 v2 routers Mika Westerberg
2023-10-05 9:27 ` [PATCH 06/10] thunderbolt: Introduce tb_port_path_direction_downstream() Mika Westerberg
2023-10-05 9:27 ` [PATCH 07/10] thunderbolt: Introduce tb_for_each_upstream_port_on_path() Mika Westerberg
2023-10-05 9:27 ` [PATCH 08/10] thunderbolt: Introduce tb_switch_depth() Mika Westerberg
2023-10-05 9:27 ` [PATCH 09/10] thunderbolt: Add support for asymmetric link Mika Westerberg
2023-10-05 9:27 ` [PATCH 10/10] thunderbolt: Configure asymmetric link if needed and bandwidth allows 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=20231005092729.3595447-1-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=gil.fine@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).