All of lore.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>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-usb@vger.kernel.org
Subject: [GIT PULL] Thunderbolt/USB4 changes for v5.18 merge window
Date: Tue, 8 Mar 2022 14:20:33 +0200	[thread overview]
Message-ID: <YidKEUcphTB4SE0E@lahna> (raw)

Hi Greg,

The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:

  Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git tags/thunderbolt-for-v5.18-rc1

for you to fetch changes up to 144c4a77a3e1e520daba85eafd28999af22e1aa5:

  thunderbolt: Rename EEPROM handling bits to match USB4 spec (2022-03-04 17:10:36 +0300)

----------------------------------------------------------------
thunderbolt: Changes for v5.18 merge window

This includes following Thunderbolt/USB4 changes for the v5.18 merge
window:

  * Improvements for Intel Alpine and Titan Ridge support
  * Replace acpi_bus_get_device() with acpi_fetch_acpi_dev()
  * Improvements around DROM handling on AMD hardware
  * A couple of cleanups.

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

----------------------------------------------------------------
Christophe JAILLET (1):
      thunderbolt: Remove useless DMA-32 fallback configuration

Mario Limonciello (5):
      thunderbolt: Retry DROM reads for more failure scenarios
      thunderbolt: Do not resume routers if UID is not set
      thunderbolt: Do not make DROM read success compulsory
      thunderbolt: Clarify register definitions for `tb_cap_plug_events`
      thunderbolt: Rename EEPROM handling bits to match USB4 spec

Mika Westerberg (3):
      thunderbolt: Disable LTTPR on Intel Titan Ridge
      thunderbolt: Add missing device ID to tb_switch_is_alpine_ridge()
      thunderbolt: Add internal xHCI connect flows for Thunderbolt 3 devices

Rafael J. Wysocki (1):
      thunderbolt: Replace acpi_bus_get_device()

 drivers/thunderbolt/acpi.c    |   4 +-
 drivers/thunderbolt/eeprom.c  |  41 ++++++++--------
 drivers/thunderbolt/lc.c      | 110 ++++++++++++++++++++++++++++++++++++++++++
 drivers/thunderbolt/nhi.c     |   3 +-
 drivers/thunderbolt/switch.c  |  81 +++++++++++++++++++++++++++++--
 drivers/thunderbolt/tb.c      |  11 +++++
 drivers/thunderbolt/tb.h      |   8 +++
 drivers/thunderbolt/tb_regs.h |  37 +++++++++-----
 drivers/thunderbolt/tunnel.c  |  10 ++++
 9 files changed, 265 insertions(+), 40 deletions(-)

             reply	other threads:[~2022-03-08 12:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 12:20 Mika Westerberg [this message]
2022-03-11 11:46 ` [GIT PULL] Thunderbolt/USB4 changes for v5.18 merge window Greg Kroah-Hartman
2022-03-11 13:45   ` Mika Westerberg
2022-03-11 14:50     ` Greg Kroah-Hartman
2022-03-11 14:54     ` 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=YidKEUcphTB4SE0E@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.