From: Benson Leung <bleung@google.com>
To: gregkh@linuxfoundation.org
Cc: enric.balletbo@collabora.com, bleung@chromium.org,
bleung@google.com, bleung@kernel.org, linux-usb@vger.kernel.org,
pmalani@chromium.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Immutable Branch between platform/chrome and USB for v5.12 merge window
Date: Tue, 2 Feb 2021 00:06:03 -0800 [thread overview]
Message-ID: <YBkH6wO07sxRDBDo@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2496 bytes --]
Hi Greg,
The following changes since commit 29b01295a829fba7399ee84afff4e64660e49f04:
usb: typec: Add typec_partner_set_pd_revision (2021-02-01 15:31:34 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/tag-ib-usb-typec-chrome-platform-cros-ec-typec-changes-for-5.12
for you to fetch changes up to 0371616d8bef6926e9aa05757f35b901268d3724:
platform/chrome: cros_ec_typec: Set opmode to PD on SOP connected (2021-02-01 23:49:54 -0800)
----------------------------------------------------------------
cros-ec-typec changes for usb for v5.12
Chrome OS EC Type-C driver features implemented this round:
* Registration of cable plug information
* Support for SOP' plug registration and altmodes
* Support for reporting number of altmodes supported by partners and plugs
* Send mux configuration ack to EC via a new host command
* Reporting SOP' and Partner PD revisions
----------------------------------------------------------------
Benson Leung (4):
Merge remote-tracking branch 'origin/cros-ec-typec-for-5.12' into ib-usb-typec-chrome-platform-cros-ec-typec-changes-for-5.12
platform/chrome: cros_ec_typec: Report SOP' PD revision from status
platform/chrome: cros_ec_typec: Set Partner PD revision from status
platform/chrome: cros_ec_typec: Set opmode to PD on SOP connected
Prashant Malani (8):
platform/chrome: cros_ec_typec: Make disc_done flag partner-only
platform/chrome: cros_ec_typec: Factor out PD identity parsing
platform/chrome: cros_ec_typec: Rename discovery struct
platform/chrome: cros_ec_typec: Register cable
platform/chrome: cros_ec_typec: Store cable plug type
platform/chrome: cros_ec_typec: Set partner num_altmodes
platform/chrome: cros_ec_typec: Register SOP' cable plug
platform/chrome: cros_ec_typec: Register plug altmodes
Utkarsh Patel (2):
platform/chrome: cros_ec_typec: Parameterize cros_typec_cmds_supported()
platform/chrome: cros_ec_typec: Send mux configuration acknowledgment to EC
drivers/platform/chrome/cros_ec_typec.c | 269 +++++++++++++++++++++----
include/linux/platform_data/cros_ec_commands.h | 17 ++
2 files changed, 243 insertions(+), 43 deletions(-)
Thanks so much!
Benson
--
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:[~2021-02-02 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 8:06 Benson Leung [this message]
2021-02-02 10:41 ` [GIT PULL] Immutable Branch between platform/chrome and USB for v5.12 merge window Enric Balletbo i Serra
2021-02-02 15:11 ` Greg KH
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=YBkH6wO07sxRDBDo@google.com \
--to=bleung@google.com \
--cc=bleung@chromium.org \
--cc=bleung@kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmalani@chromium.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 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.