Linux-USB Archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org,
	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>
Subject: [GIT PULL] USB4/Thunderbolt changes for v6.10 merge window
Date: Fri, 10 May 2024 08:05:24 +0300	[thread overview]
Message-ID: <20240510050524.GB4162345@black.fi.intel.com> (raw)

Hi Greg,

The following changes since commit fec50db7033ea478773b159e0e2efb135270e3b7:

  Linux 6.9-rc3 (2024-04-07 13:22:46 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git tags/thunderbolt-for-v6.10-rc1

for you to fetch changes up to a3dc6d82de9bd88871dbc4ac511409e69ecacbfb:

  thunderbolt: Correct trace output of firmware connection manager packets (2024-04-29 07:47:54 +0300)

----------------------------------------------------------------
thunderbolt: Changes for v6.10 merge window

This includes following USB4/Thunderbolt changes for the v6.10 merge
window:

  - Enable NVM firmare upgrade on Intel Maple Ridge Thunderbolt 4
    controller
  - Improve USB3 tunnel bandwidth calculation
  - Improve sideband access
  - Minor cleanups and fixes.

All these have been in linux-next with no reported issues.

----------------------------------------------------------------
Alex James (1):
      thunderbolt: Enable NVM upgrade support on Intel Maple Ridge

Gil Fine (4):
      thunderbolt: Fix calculation of consumed USB3 bandwidth on a path
      thunderbolt: Allow USB3 bandwidth to be lower than maximum supported
      thunderbolt: Fix uninitialized variable in tb_tunnel_alloc_usb3()
      thunderbolt: Fix kernel-doc for tb_tunnel_alloc_dp()

Mika Westerberg (6):
      thunderbolt: Use correct error code with ERROR_NOT_SUPPORTED
      thunderbolt: Get rid of TB_CFG_PKG_PREPARE_TO_SLEEP
      thunderbolt: Increase sideband access polling delay
      thunderbolt: No need to loop over all retimers if access fails
      thunderbolt: There are only 5 basic router registers in pre-USB4 routers
      thunderbolt: Correct trace output of firmware connection manager packets

 drivers/thunderbolt/debugfs.c |  2 +-
 drivers/thunderbolt/icm.c     |  1 +
 drivers/thunderbolt/retimer.c | 12 ++++++++----
 drivers/thunderbolt/tb.c      |  9 +++++----
 drivers/thunderbolt/tb_msgs.h |  6 ------
 drivers/thunderbolt/trace.h   | 13 +++++++++++--
 drivers/thunderbolt/tunnel.c  | 39 +++++++++++++++++----------------------
 drivers/thunderbolt/usb4.c    | 22 +++++++++++++++-------
 drivers/thunderbolt/xdomain.c |  2 +-
 include/linux/thunderbolt.h   |  1 -
 10 files changed, 59 insertions(+), 48 deletions(-)

             reply	other threads:[~2024-05-10  5:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10  5:05 Mika Westerberg [this message]
2024-05-10  9:25 ` [GIT PULL] USB4/Thunderbolt changes for v6.10 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=20240510050524.GB4162345@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).