From: Pi-Hsun Shih <pihsun@chromium.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Pi-Hsun Shih <pihsun@chromium.org>,
Nicolas Boichat <drinkcat@chromium.org>,
Benson Leung <bleung@chromium.org>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Fabien Lahoudere <fabien.lahoudere@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org (open list),
Tzung-Bi Shih <tzungbi@google.com>
Subject: [PATCH v2 0/2] Add support for voltage regulator on ChromeOS EC.
Date: Wed, 10 Jun 2020 15:56:42 +0800 [thread overview]
Message-ID: <20200610075649.209852-1-pihsun@chromium.org> (raw)
Add support for controlling voltage regulator that is connected and
controlled by ChromeOS EC. Kernel controls these regulators through
newly added EC host commands.
Changes from v1:
* Change compatible string to google,regulator-cros-ec.
* Use reg property in device tree.
* Change license for dt binding according to checkpatch.pl.
* Address comments on code styles.
Pi-Hsun Shih (2):
dt-bindings: regulator: Add DT binding for cros-ec-regulator
regulator: Add driver for cros-ec-regulator
.../bindings/regulator/cros-ec-regulator.yaml | 43 +++
drivers/regulator/Kconfig | 7 +
drivers/regulator/Makefile | 1 +
drivers/regulator/cros-ec-regulator.c | 262 ++++++++++++++++++
.../linux/platform_data/cros_ec_commands.h | 82 ++++++
5 files changed, 395 insertions(+)
create mode 100644 Documentation/devicetree/bindings/regulator/cros-ec-regulator.yaml
create mode 100644 drivers/regulator/cros-ec-regulator.c
base-commit: 5b14671be58d0084e7e2d1cc9c2c36a94467f6e0
--
2.27.0.278.ge193c7cf3a9-goog
next reply other threads:[~2020-06-10 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 7:56 Pi-Hsun Shih [this message]
2020-06-10 7:56 ` [PATCH v2 1/2] dt-bindings: regulator: Add DT binding for cros-ec-regulator Pi-Hsun Shih
2020-06-10 7:56 ` [PATCH v2 2/2] regulator: Add driver " Pi-Hsun Shih
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=20200610075649.209852-1-pihsun@chromium.org \
--to=pihsun@chromium.org \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=fabien.lahoudere@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzungbi@google.com \
/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;
as well as URLs for NNTP newsgroup(s).