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>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-usb@vger.kernel.org
Subject: [GIT PULL] Thunderbolt/USB4 changes for v5.17 merge window
Date: Mon, 3 Jan 2022 12:52:14 +0200 [thread overview]
Message-ID: <YdLVXlwnU+QNxaHZ@lahna> (raw)
Hi Greg,
The following changes since commit 0fcfb00b28c0b7884635dacf38e46d60bf3d4eb1:
Linux 5.16-rc4 (2021-12-05 14:08:22 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git tags/thunderbolt-for-v5.17-rc1
for you to fetch changes up to fa487b2a900d7b22fe7db678d2134fbf56ae9da0:
thunderbolt: Add module parameter for CLx disabling (2021-12-28 10:43:56 +0300)
----------------------------------------------------------------
thunderbolt: Changes for v5.17 merge window
This includes following Thunderbolt/USB4 changes for the v5.17 merge
window:
* Enable low-power link state (CL0s) for USB4 and Intel Titan Ridge
devices
* Add support for TMU (Time Management Unit) uni-directional mode
* Power management improvements (suspend-to-disk, runtime PM)
* USB4 compatibility fixes
* Minor fixes and cleanups.
All these have been in linux-next with no reported issues.
----------------------------------------------------------------
Andy Shevchenko (1):
thunderbolt: Do not dereference fwnode in struct device
Gil Fine (7):
thunderbolt: Add TMU uni-directional mode
thunderbolt: Add CL0s support for USB4 routers
thunderbolt: Move usb4_switch_wait_for_bit() to switch.c
thunderbolt: Implement TMU time disruption for Intel Titan Ridge
thunderbolt: Rename Intel TB_VSE_CAP_IECS capability
thunderbolt: Enable CL0s for Intel Titan Ridge
thunderbolt: Add module parameter for CLx disabling
Kees Cook (1):
thunderbolt: xdomain: Avoid potential stack OOB read
Mika Westerberg (6):
thunderbolt: Runtime PM activate both ends of the device link
thunderbolt: Tear down existing tunnels when resuming from hibernate
thunderbolt: Runtime resume USB4 port when retimers are scanned
thunderbolt: Do not allow subtracting more NFC credits than configured
thunderbolt: Do not program path HopIDs for USB4 routers
thunderbolt: Add debug logging of DisplayPort resource allocation
Xiaoke Wang (1):
thunderbolt: Check return value of kmemdup() in icm_handle_event()
drivers/thunderbolt/acpi.c | 15 +-
drivers/thunderbolt/icm.c | 7 +-
drivers/thunderbolt/lc.c | 24 ++
drivers/thunderbolt/path.c | 42 ++--
drivers/thunderbolt/retimer.c | 28 ++-
drivers/thunderbolt/switch.c | 493 +++++++++++++++++++++++++++++++++++++++++-
drivers/thunderbolt/tb.c | 91 ++++++--
drivers/thunderbolt/tb.h | 106 ++++++++-
drivers/thunderbolt/tb_msgs.h | 47 ++--
drivers/thunderbolt/tb_regs.h | 113 +++++++---
drivers/thunderbolt/tmu.c | 337 ++++++++++++++++++++++++-----
drivers/thunderbolt/tunnel.c | 27 ++-
drivers/thunderbolt/tunnel.h | 9 +-
drivers/thunderbolt/usb4.c | 52 +++--
drivers/thunderbolt/xdomain.c | 16 +-
15 files changed, 1203 insertions(+), 204 deletions(-)
next reply other threads:[~2022-01-03 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 10:52 Mika Westerberg [this message]
2022-01-03 12:22 ` [GIT PULL] Thunderbolt/USB4 changes for v5.17 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=YdLVXlwnU+QNxaHZ@lahna \
--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