From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Yehezkel Bernat <YehezkelShB@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Lukas Wunner <lukas@wunner.de>,
Andreas Noever <andreas.noever@gmail.com>,
linux-usb@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [GIT PULL] USB4/Thunderbolt changes for v6.8 merge window
Date: Tue, 2 Jan 2024 14:39:54 +0200 [thread overview]
Message-ID: <20240102123954.GK2543524@black.fi.intel.com> (raw)
Hi Greg,
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git tags/thunderbolt-for-v6.8-rc1
for you to fetch changes up to 04b99eac389adc6485f7913d83ec9ed68bbc8326:
thunderbolt: Reduce retry timeout to speed up boot for some devices (2023-12-22 13:00:26 +0200)
----------------------------------------------------------------
thunderbolt: Changes for v6.8 merge window
This includes following USB4/Thunderbolt changes for the v6.8 merge
window:
- Intel Lunar Lake support
- PCIe tunneling improvements
- DisplayPort tunneling improvements
- Asymmetric switching improvements
- Couple of minor fixes and cleanups.
All these have been in linux-next with no reported issues.
----------------------------------------------------------------
Colin Ian King (1):
thunderbolt: Remove duplicated re-assignment of pointer 'out'
Gil Fine (8):
thunderbolt: Handle lane bonding of Gen 4 XDomain links properly
thunderbolt: Move width_name() helper to tb.h
thunderbolt: Log XDomain link speed and width
thunderbolt: Transition link to asymmetric only when both sides support it
thunderbolt: Improve logging when DisplayPort resource is added due to hotplug
thunderbolt: Make PCIe tunnel setup and teardown follow CM guide
thunderbolt: Disable PCIe extended encapsulation upon teardown properly
thunderbolt: Keep link as asymmetric if preferred by hardware
Mika Westerberg (4):
thunderbolt: Unwind TMU configuration if tb_switch_set_tmu_mode_params() fails
thunderbolt: Disable CL states only when actually needed
thunderbolt: Use tb_dp_read_cap() to read DP_COMMON_CAP as well
thunderbolt: Add support for Intel Lunar Lake
Werner Sembach (1):
thunderbolt: Reduce retry timeout to speed up boot for some devices
drivers/thunderbolt/icm.c | 2 +-
drivers/thunderbolt/nhi.c | 4 +++
drivers/thunderbolt/nhi.h | 2 ++
drivers/thunderbolt/switch.c | 33 +++++++++----------
drivers/thunderbolt/tb.c | 74 +++++++++++++++++++++++++++++--------------
drivers/thunderbolt/tb.h | 18 +++++++++++
drivers/thunderbolt/tmu.c | 2 +-
drivers/thunderbolt/tunnel.c | 46 +++++++++++++++++++--------
drivers/thunderbolt/xdomain.c | 54 ++++++++++++++++++++++++++++++-
9 files changed, 176 insertions(+), 59 deletions(-)
next reply other threads:[~2024-01-02 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 12:39 Mika Westerberg [this message]
2024-01-02 13:25 ` [GIT PULL] USB4/Thunderbolt changes for v6.8 merge window Greg Kroah-Hartman
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=20240102123954.GK2543524@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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