Chrome platform driver development
 help / color / mirror / Atom feed
From: Benson Leung <bleung@google.com>
To: torvalds@linux-foundation.org
Cc: pmalani@chromium.org, bleung@chromium.org, bleung@google.com,
	bleung@kernel.org, chrome-platform@lists.linux.dev,
	linux-kernel@vger.kernel.org, tzungbi@kernel.org
Subject: [GIT PULL] chrome-platform changes for v5.18
Date: Fri, 1 Apr 2022 18:18:13 -0700	[thread overview]
Message-ID: <YkekVRh9Ixdfa5qL@google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2913 bytes --]

Hi Linus,

Here's chrome-platform's changes for v5.18-rc1.

Of note, the last two commits of this PR had to be reworded (actually just
the second to last one) since it hit linux-next for a minor commit message
fixup. Content wise, the two are the same as they are on linux-next right now.

Thanks,
Benson

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/chrome-platform/linux.git tags/tag-chrome-platform-for-v5.18

for you to fetch changes up to 0e8eb5e8acbad19ac2e1856b2fb2320184299b33:

  platform/chrome: cros_ec_debugfs: detach log reader wq from devm (2022-03-31 16:56:48 -0700)

----------------------------------------------------------------
chrome platform changes for 5.18

cros_ec_typec:
* platform/chrome: cros_ec_typec: Check for EC device - Fix a crash when using
  the cros_ec_typec driver on older hardware not capable of typec commands.
* Make try power role optional.
* Mux configuration reorganization series from Prashant.

cros_ec_debugfs:
* Fix use after free. Thanks Tzung-bi.

sensorhub:
* cros_ec_sensorhub fixup - Split trace include file

misc:
* Add new mailing list for chrome-platform development.
  chrome-platform@lists.linux.dev. Now with patchwork!

----------------------------------------------------------------
Benson Leung (1):
      MAINTAINERS: platform-chrome: Add new chrome-platform@lists.linux.dev list

Gwendal Grignou (1):
      platform: chrome: Split trace include file

Prashant Malani (6):
      platform/chrome: cros_ec_typec: Make try power role optional
      platform/chrome: cros_ec_typec: Check for EC device
      platform/chrome: cros_ec_typec: Move mux flag checks
      platform/chrome: cros_ec_typec: Get mux state inside configure_mux
      platform/chrome: cros_ec_typec: Configure muxes at start of port update
      platform/chrome: cros_ec_typec: Update mux flags during partner removal

Tzung-Bi Shih (1):
      platform/chrome: cros_ec_debugfs: detach log reader wq from devm

 MAINTAINERS                                       |   5 +
 drivers/platform/chrome/Makefile                  |   3 +-
 drivers/platform/chrome/cros_ec_debugfs.c         |  12 +--
 drivers/platform/chrome/cros_ec_sensorhub_ring.c  |   3 +-
 drivers/platform/chrome/cros_ec_sensorhub_trace.h | 123 ++++++++++++++++++++++
 drivers/platform/chrome/cros_ec_trace.h           |  95 -----------------
 drivers/platform/chrome/cros_ec_typec.c           |  97 +++++++++--------
 7 files changed, 186 insertions(+), 152 deletions(-)
 create mode 100644 drivers/platform/chrome/cros_ec_sensorhub_trace.h

-- 
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2022-04-02  1:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02  1:18 Benson Leung [this message]
2022-04-02 18:10 ` [GIT PULL] chrome-platform changes for v5.18 pr-tracker-bot
2022-04-04 17:02 ` patchwork-bot+chrome-platform
2022-04-04 17:14 ` patchwork-bot+chrome-platform

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=YkekVRh9Ixdfa5qL@google.com \
    --to=bleung@google.com \
    --cc=bleung@chromium.org \
    --cc=bleung@kernel.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmalani@chromium.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tzungbi@kernel.org \
    /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