From: Benson Leung <bleung@google.com>
To: Jon Flatley <jflat@chromium.org>,
heikki.krogerus@linux.intel.com, heikki.krogerus@intel.com,
enric.balletbo@collabora.com
Cc: linux-kernel@vger.kernel.org, bleung@chromium.org,
groeck@chromium.org, sre@kernel.org, pmalani@chromium.org
Subject: Re: [PATCH 0/3] ChromeOS EC USB-C Connector Class
Date: Wed, 13 Nov 2019 09:51:27 -0800 [thread overview]
Message-ID: <20191113175127.GA171004@google.com> (raw)
In-Reply-To: <20191113031044.136232-1-jflat@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
Hi Jon,
Thanks for posting this.
Adding Heikki, the typec connector class maintainer, and Enric, co-maintainer
of platform/chrome.
Benson
On Tue, Nov 12, 2019 at 07:10:41PM -0800, Jon Flatley wrote:
> This patch set adds a basic implementation of the USB-C connector class for
> devices using the ChromeOS EC. On ACPI devices an additional ACPI driver is
> necessary to receive USB-C PD host events from the PD EC device "GOOG0003".
> Incidentally, this ACPI driver adds notifications for events that
> cros-usbpd-charger has been missing, so fix that while we're at it.
>
> Jon Flatley (3):
> platform: chrome: Add cros-ec-usbpd-notify driver
> power: supply: cros-ec-usbpd-charger: Fix host events
> platform: chrome: Added cros-ec-typec driver
>
> drivers/mfd/cros_ec_dev.c | 7 +-
> drivers/platform/chrome/Kconfig | 20 +
> drivers/platform/chrome/Makefile | 2 +
> drivers/platform/chrome/cros_ec_typec.c | 457 ++++++++++++++++++
> .../platform/chrome/cros_ec_usbpd_notify.c | 156 ++++++
> drivers/power/supply/Kconfig | 2 +-
> drivers/power/supply/cros_usbpd-charger.c | 45 +-
> .../platform_data/cros_ec_usbpd_notify.h | 40 ++
> 8 files changed, 696 insertions(+), 33 deletions(-)
> create mode 100644 drivers/platform/chrome/cros_ec_typec.c
> create mode 100644 drivers/platform/chrome/cros_ec_usbpd_notify.c
> create mode 100644 include/linux/platform_data/cros_ec_usbpd_notify.h
>
> --
> 2.24.0.432.g9d3f5f5b63-goog
>
--
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 prev parent reply other threads:[~2019-11-13 17:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 3:10 [PATCH 0/3] ChromeOS EC USB-C Connector Class Jon Flatley
2019-11-13 3:10 ` [PATCH 1/3] platform: chrome: Add cros-ec-usbpd-notify driver Jon Flatley
2019-11-14 21:43 ` Enric Balletbo Serra
2019-11-13 3:10 ` [PATCH 2/3] power: supply: cros-ec-usbpd-charger: Fix host events Jon Flatley
2019-11-14 21:53 ` Enric Balletbo Serra
2019-11-13 3:10 ` [PATCH 3/3] platform: chrome: Added cros-ec-typec driver Jon Flatley
2019-11-13 12:55 ` kbuild test robot
2019-11-13 17:23 ` Jon Flatley
2019-11-14 0:55 ` [kbuild-all] " Rong Chen
2019-11-14 1:07 ` Guenter Roeck
2019-11-14 16:53 ` Heikki Krogerus
2019-11-13 17:51 ` Benson Leung [this message]
2019-11-13 18:25 ` [PATCH 0/3] ChromeOS EC USB-C Connector Class Heikki Krogerus
2019-11-14 1:09 ` Jon Flatley
2019-11-14 15:24 ` Heikki Krogerus
2019-11-14 21:00 ` Jon Flatley
2019-11-15 16:41 ` Heikki Krogerus
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=20191113175127.GA171004@google.com \
--to=bleung@google.com \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=jflat@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=sre@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