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: Andreas Noever <andreas.noever@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Lukas Wunner <lukas@wunner.de>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Thunderbolt changes for v5.4
Date: Sat, 31 Aug 2019 16:56:16 +0300	[thread overview]
Message-ID: <20190831135616.GR3177@lahna.fi.intel.com> (raw)

Hi Greg,

The following changes since commit e21a712a9685488f5ce80495b37b9fdbe96c230d:

  Linux 5.3-rc3 (2019-08-04 18:40:12 -0700)

are available in the Git repository at:

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

for you to fetch changes up to dfda204198848b47bdb98ab83b94dbb7c7692b55:

  ACPI / property: Add two new Thunderbolt property GUIDs to the list (2019-08-26 12:15:11 +0300)

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

The biggest change is the addition of Intel Ice Lake integrated
Thunderbolt support. There are also a couple of smaller changes like
converting the driver to use better device property interface and use
correct format string in service key attribute.

----------------------------------------------------------------
Andy Shevchenko (1):
      thunderbolt: Switch to use device_property_count_uXX()

J. Bruce Fields (1):
      thunderbolt: Show key using %*pE not %*pEp

Mika Westerberg (8):
      thunderbolt: Correct path indices for PCIe tunnel
      thunderbolt: Move NVM upgrade support flag to struct icm
      thunderbolt: Use 32-bit writes when writing ring producer/consumer
      thunderbolt: Do not fail adding switch if some port is not implemented
      thunderbolt: Hide switch attributes that are not set
      thunderbolt: Expose active parts of NVM even if upgrade is not supported
      thunderbolt: Add support for Intel Ice Lake
      ACPI / property: Add two new Thunderbolt property GUIDs to the list

 drivers/acpi/property.c        |   6 ++
 drivers/thunderbolt/Makefile   |   2 +-
 drivers/thunderbolt/ctl.c      |  23 ++++-
 drivers/thunderbolt/eeprom.c   |   6 +-
 drivers/thunderbolt/icm.c      | 194 +++++++++++++++++++++++++++++++++++++----
 drivers/thunderbolt/nhi.c      | 134 +++++++++++++++++++++++++---
 drivers/thunderbolt/nhi.h      |  22 +++++
 drivers/thunderbolt/nhi_ops.c  | 179 +++++++++++++++++++++++++++++++++++++
 drivers/thunderbolt/nhi_regs.h |  37 ++++++++
 drivers/thunderbolt/switch.c   |  52 ++++++++---
 drivers/thunderbolt/tb_msgs.h  |  16 +++-
 drivers/thunderbolt/tunnel.c   |   4 +-
 drivers/thunderbolt/xdomain.c  |   2 +-
 include/linux/thunderbolt.h    |   2 +
 14 files changed, 624 insertions(+), 55 deletions(-)
 create mode 100644 drivers/thunderbolt/nhi_ops.c

             reply	other threads:[~2019-08-31 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-31 13:56 Mika Westerberg [this message]
2019-09-03 19:56 ` [GIT PULL] Thunderbolt changes for v5.4 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=20190831135616.GR3177@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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.