public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
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.14 merge window
Date: Tue, 14 Jan 2025 12:32:42 +0200	[thread overview]
Message-ID: <20250114103242.GM3713119@black.fi.intel.com> (raw)

Hi Greg,

The following changes since commit 4bbf9020becbfd8fc2c3da790855b7042fad455b:

  Linux 6.13-rc4 (2024-12-22 13:22:21 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 43d84701d2aa147eab39b529919ffaf35f724bbb:

  thunderbolt: Expose router DROM through debugfs (2025-01-05 10:35:03 +0200)

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

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

  - Add debugfs write capability to path config spaces.
  - Expose router DROM through debugfs.
  - Increase DPRX capabilities read timeout to support runtime
    suspending of graphics driver.
  - Handle DisplayPort tunnel activation asynchronously.
  - Small cleanups.

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

----------------------------------------------------------------
Gil Fine (1):
      thunderbolt: debugfs: Add write capability to path config space

Mika Westerberg (13):
      thunderbolt: Drop doubled empty line from ctl.h
      thunderbolt: Log config space when invalid config space reply is received
      thunderbolt: Debug log an invalid config space reply just once
      thunderbolt: Increase DPRX capabilities read timeout
      thunderbolt: Make tb_tunnel_one_dp() return void
      thunderbolt: Show path name in debug log when path is deactivated
      thunderbolt: Rework how tunnel->[init|deinit] hooks are called
      thunderbolt: Drop tb_tunnel_restart()
      thunderbolt: Pass reason to tb_dp_resource_unavailable()
      thunderbolt: Move forward declarations in one place
      thunderbolt: Rework tb_tunnel_consumed_bandwidth()
      thunderbolt: Handle DisplayPort tunnel activation asynchronously
      thunderbolt: Expose router DROM through debugfs

 drivers/thunderbolt/ctl.c     |  11 +-
 drivers/thunderbolt/ctl.h     |   1 -
 drivers/thunderbolt/debugfs.c |  67 +++++--
 drivers/thunderbolt/eeprom.c  |  78 ++++----
 drivers/thunderbolt/path.c    |   4 +-
 drivers/thunderbolt/tb.c      | 196 ++++++++++++++------
 drivers/thunderbolt/tb.h      |   5 +
 drivers/thunderbolt/test.c    |  90 +++++-----
 drivers/thunderbolt/tunnel.c  | 406 ++++++++++++++++++++++++++----------------
 drivers/thunderbolt/tunnel.h  |  61 ++++++-
 10 files changed, 600 insertions(+), 319 deletions(-)

             reply	other threads:[~2025-01-14 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 10:32 Mika Westerberg [this message]
2025-01-15 15:17 ` [GIT PULL] USB4/Thunderbolt changes for v6.14 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=20250114103242.GM3713119@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