From: Mathew King <mathewk@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: Mathew King <mathewk@chromium.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Benson Leung <bleung@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-pm@vger.kernel.org
Subject: [PATCH v0 0/2] Type-C charger support using power_supply
Date: Mon, 20 Apr 2020 10:36:55 -0600 [thread overview]
Message-ID: <20200420163657.60650-1-mathewk@chromium.org> (raw)
I am looking to expose Type-C charging ports using a power_supply class. In this
patch series I have done this by creating a config option to enable this by
adding support directly into the typec driver. I would like some feedback on
this general approach.
I have been testing on a system that uses an ACPI implementation of UCSI and
things are working as expected.
Mathew King (2):
typec: Move typec class structs into a header file
typec: Add Type-C charger
drivers/usb/typec/Kconfig | 11 ++
drivers/usb/typec/Makefile | 1 +
drivers/usb/typec/charger.c | 204 ++++++++++++++++++++++++++++++++++++
drivers/usb/typec/charger.h | 33 ++++++
drivers/usb/typec/class.c | 108 ++++++++-----------
drivers/usb/typec/class.h | 63 +++++++++++
6 files changed, 356 insertions(+), 64 deletions(-)
create mode 100644 drivers/usb/typec/charger.c
create mode 100644 drivers/usb/typec/charger.h
create mode 100644 drivers/usb/typec/class.h
--
2.26.1.301.g55bc3eb7cb9-goog
next reply other threads:[~2020-04-20 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 16:36 Mathew King [this message]
2020-04-20 16:36 ` [PATCH v0 1/2] typec: Move typec class structs into a header file Mathew King
2020-04-20 16:36 ` [PATCH v0 2/2] typec: Add Type-C charger Mathew King
2020-04-21 8:44 ` Adam Thomson
2020-04-21 12:41 ` Heikki Krogerus
2020-04-21 15:56 ` Mat King
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=20200420163657.60650-1-mathewk@chromium.org \
--to=mathewk@chromium.org \
--cc=bleung@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.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