From: Benson Leung <bleung@google.com>
To: torvalds@linux-foundation.org
Cc: enric.balletbo@collabora.com, bleung@chromium.org,
bleung@google.com, bleung@kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] chrome-platform changes for v5.11
Date: Tue, 22 Dec 2020 16:29:21 -0800 [thread overview]
Message-ID: <X+KPYZIAZXFOI/YD@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1921 bytes --]
Hi Linus,
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
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.11
for you to fetch changes up to 6ae9b5ffcaeba64c290dfb8bd7b0194b1fdf0c92:
platform/chrome: cros_ec_typec: Tolerate unrecognized mux flags (2020-12-10 13:05:16 -0800)
----------------------------------------------------------------
chrome platform changes for 5.11
cros_ec_typec:
* A series from Prashant for Type-C to implement TYPEC_STATUS, parsing USB PD
Partner ID VDOs, and registering partner altmodes.
cros_ec misc:
* Don't treat RTC events as wakeup sources in cros_ec_proto
----------------------------------------------------------------
Prashant Malani (8):
platform/chrome: cros_ec_typec: Relocate set_port_params_v*() functions
platform/chrome: cros_ec_typec: Fix remove partner logic
platform/chrome: cros_ec_typec: Clear partner identity on device removal
platform/chrome: cros_ec: Import Type C host commands
platform/chrome: cros_ec_typec: Introduce TYPEC_STATUS
platform/chrome: cros_ec_typec: Parse partner PD ID VDOs
platform/chrome: cros_ec_typec: Register partner altmodes
platform/chrome: cros_ec_typec: Tolerate unrecognized mux flags
Stephen Boyd (1):
platform/chrome: Don't treat RTC events as wakeup sources
drivers/platform/chrome/cros_ec_proto.c | 14 +-
drivers/platform/chrome/cros_ec_typec.c | 336 +++++++++++++++++++------
include/linux/platform_data/cros_ec_commands.h | 155 ++++++++++++
3 files changed, 427 insertions(+), 78 deletions(-)
--
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 --]
next reply other threads:[~2020-12-23 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 0:29 Benson Leung [this message]
2020-12-23 23:41 ` pr-tracker-bot
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=X+KPYZIAZXFOI/YD@google.com \
--to=bleung@google.com \
--cc=bleung@chromium.org \
--cc=bleung@kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®