From: Zev Weiss <zev@bewilderbeest.net>
To: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>
Cc: Zev Weiss <zev@bewilderbeest.net>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
openbmc@lists.ozlabs.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org
Subject: [PATCH v2 0/2] extcon: Add extcon-regulator driver
Date: Thu, 5 May 2022 16:25:55 -0700 [thread overview]
Message-ID: <20220505232557.10936-1-zev@bewilderbeest.net> (raw)
Hello,
This is a restructured v2 of a series adding support for
regulator-supplied power output connectors.
Changes since v1 [0, 1]:
- Dropped regulator-external-output DT property [Mark]
- Moved DT binding to connector/regulator-connector.yaml [Krzysztof]
- Dropped EXTERNAL_GET type and other regulator-core changes
This driver aims to support hardware where a regulator supplies a
power output connector, such as a power outlet on a DC power
distribution unit (PDU). (The specific system I'm targeting at the
moment is the Delta AHE-50DC Open19 power shelf [2], for which I'm
working on a port of OpenBMC.)
Patch 1 adds the regulator-connector DT binding, with a single
property specifying the regulator supplying the connector's output
power, and patch 2 adds an extcon driver (extcon-regulator). The
driver currently doesn't actually do much extcon-wise, because the
AHE-50DC hardware is quite minimal and doesn't really offer much for
it to do, but if other similar devices in the future do have
additional functionality to support (such as a presence-detection
mechanism) the driver can be extended to add that.
Thanks,
Zev
[0] https://lore.kernel.org/openbmc/20220504065041.6718-1-zev@bewilderbeest.net/
[1] https://lore.kernel.org/openbmc/20220504065252.6955-1-zev@bewilderbeest.net/
[2] https://www.open19.org/marketplace/delta-16kw-power-shelf/
Zev Weiss (2):
dt-bindings: connector: Add regulator-connector binding
extcon: Add extcon-regulator driver
.../ABI/testing/sysfs-driver-extcon-regulator | 8 ++
.../connector/regulator-connector.yaml | 38 +++++
MAINTAINERS | 8 ++
drivers/extcon/Kconfig | 8 ++
drivers/extcon/Makefile | 1 +
drivers/extcon/extcon-regulator.c | 133 ++++++++++++++++++
6 files changed, 196 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-driver-extcon-regulator
create mode 100644 Documentation/devicetree/bindings/connector/regulator-connector.yaml
create mode 100644 drivers/extcon/extcon-regulator.c
--
2.36.0
next reply other threads:[~2022-05-05 23:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 23:25 Zev Weiss [this message]
2022-05-05 23:25 ` [PATCH v2 1/2] dt-bindings: connector: Add regulator-connector binding Zev Weiss
2022-05-17 0:15 ` Rob Herring
2022-05-05 23:25 ` [PATCH v2 2/2] extcon: Add extcon-regulator driver Zev Weiss
2022-05-09 12:24 ` Chanwoo Choi
2022-05-09 15:24 ` Mark Brown
2022-05-17 1:03 ` Zev Weiss
2022-05-17 3:15 ` Chanwoo Choi
2022-05-17 10:07 ` Zev Weiss
2022-05-17 18:15 ` Chanwoo Choi
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=20220505232557.10936-1-zev@bewilderbeest.net \
--to=zev@bewilderbeest.net \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).