From: Max Krummenacher <max.oss.09@gmail.com>
To: max.krummenacher@toradex.com
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
linux-pm@vger.kernel.org,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Mark Brown <broonie@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Kevin Hilman <khilman@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 1/5] dt-bindings: power: Add bindings for a power domain controlled by a regulator
Date: Thu, 9 Jun 2022 17:08:47 +0200 [thread overview]
Message-ID: <20220609150851.23084-2-max.oss.09@gmail.com> (raw)
In-Reply-To: <20220609150851.23084-1-max.oss.09@gmail.com>
From: Max Krummenacher <max.krummenacher@toradex.com>
Adds binding for a power domain provider which uses a regulator to control
the power domain.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
---
.../power/regulator-power-domain.yaml | 58 +++++++++++++++++++
1 file changed, 58 insertions(+)
create mode 100644 Documentation/devicetree/bindings/power/regulator-power-domain.yaml
diff --git a/Documentation/devicetree/bindings/power/regulator-power-domain.yaml b/Documentation/devicetree/bindings/power/regulator-power-domain.yaml
new file mode 100644
index 000000000000..2b49c4f2f866
--- /dev/null
+++ b/Documentation/devicetree/bindings/power/regulator-power-domain.yaml
@@ -0,0 +1,58 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/power/regulator-power-domain.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Power domain controlled by a regulator
+
+maintainers:
+ - Max Krummenacher <max.krummenacher@toradex.com>
+
+description: |+
+ Power domain provider which uses a regulator to control
+ the power domain.
+
+allOf:
+ - $ref: "power-domain.yaml#"
+
+properties:
+ compatible:
+ enum:
+ - regulator-pm-pd
+
+ power-supply:
+ description: The regulator used to control the power domain.
+
+ label:
+ description: Human readable string defining the domain.
+
+ "#power-domain-cells":
+ const: 0
+
+ power-domains:
+ maxItems: 1
+
+required:
+ - compatible
+ - "#power-domain-cells"
+ - power-supply
+
+additionalProperties: true
+
+examples:
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+ reg_pd_sleep_moci: regulator-sleep-moci {
+ compatible = "regulator-fixed";
+ enable-active-high;
+ gpio = <&gpio5 1 GPIO_ACTIVE_HIGH>;
+ regulator-name = "CTRL_SLEEP_MOCI";
+ };
+
+ pd_sleep_moci: power-sleep-moci {
+ compatible = "regulator-pm-pd";
+ power-supply = <®_pd_sleep_moci>;
+ label = "pd_sleep_moci";
+ #power-domain-cells = <0>;
+ };
--
2.20.1
next prev parent reply other threads:[~2022-06-09 15:09 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 15:08 [PATCH v1 0/5] power: domain: Add driver for a PM domain provider which controls Max Krummenacher
2022-06-09 15:08 ` Max Krummenacher
2022-06-09 15:08 ` Max Krummenacher [this message]
2022-06-10 2:57 ` [PATCH v1 1/5] dt-bindings: power: Add bindings for a power domain controlled by a regulator Rob Herring
2022-06-15 15:19 ` Max Krummenacher
2022-06-15 17:16 ` Krzysztof Kozlowski
2022-06-14 7:23 ` Geert Uytterhoeven
2022-06-15 15:18 ` Max Krummenacher
2022-06-09 15:08 ` [PATCH v1 2/5] pm: add regulator power domain controller Max Krummenacher
2022-06-09 15:08 ` [PATCH v1 3/5] MAINTAINERS: add REGULATOR POWER DOMAIN Max Krummenacher
2022-06-09 15:08 ` [RFC PATCH v1 4/5] arm64: defconfig: Enable generic power domain controller controlling a regulator Max Krummenacher
2022-06-09 15:08 ` Max Krummenacher
2022-06-09 15:08 ` [RFC PATCH v1 5/5] ARM64: verdin-imx8mm: use regulator power domain to model sleep-moci Max Krummenacher
2022-06-09 15:08 ` Max Krummenacher
2022-06-14 7:29 ` Geert Uytterhoeven
2022-06-14 7:29 ` Geert Uytterhoeven
2022-06-15 15:32 ` Max Krummenacher
2022-06-15 15:32 ` Max Krummenacher
2022-06-13 19:15 ` [PATCH v1 0/5] power: domain: Add driver for a PM domain provider which controls Rob Herring
2022-06-13 19:15 ` Rob Herring
2022-06-14 7:22 ` Geert Uytterhoeven
2022-06-14 7:22 ` Geert Uytterhoeven
2022-06-15 16:10 ` Max Krummenacher
2022-06-15 16:10 ` Max Krummenacher
2022-06-15 17:15 ` Krzysztof Kozlowski
2022-06-15 17:15 ` Krzysztof Kozlowski
2022-06-15 17:31 ` Marcel Ziswiler
2022-06-15 17:31 ` Marcel Ziswiler
2022-06-15 17:37 ` Krzysztof Kozlowski
2022-06-15 17:37 ` Krzysztof Kozlowski
2022-06-15 18:13 ` Marcel Ziswiler
2022-06-15 18:13 ` Marcel Ziswiler
2022-06-15 18:48 ` Dmitry Baryshkov
2022-06-15 18:48 ` Dmitry Baryshkov
2022-06-15 20:48 ` Krzysztof Kozlowski
2022-06-15 20:48 ` Krzysztof Kozlowski
2022-06-15 18:24 ` Robin Murphy
2022-06-15 18:24 ` Robin Murphy
2022-06-15 19:12 ` Mark Brown
2022-06-15 19:12 ` Mark Brown
2022-06-15 21:14 ` Ulf Hansson
2022-06-15 21:14 ` Ulf Hansson
2022-06-16 12:50 ` Linus Walleij
2022-06-16 12:50 ` Linus Walleij
2022-06-23 16:14 ` Max Krummenacher
2022-06-23 16:14 ` Max Krummenacher
2022-07-13 11:43 ` Ulf Hansson
2022-07-13 11:43 ` Ulf Hansson
2022-07-18 9:49 ` Linus Walleij
2022-07-18 9:49 ` Linus Walleij
2022-07-26 16:03 ` Francesco Dolcini
2022-07-26 16:03 ` Francesco Dolcini
2022-07-28 9:37 ` Ulf Hansson
2022-07-28 9:37 ` Ulf Hansson
2022-07-28 11:21 ` Francesco Dolcini
2022-07-28 11:21 ` Francesco Dolcini
2022-08-26 13:50 ` Ulf Hansson
2022-08-26 13:50 ` Ulf Hansson
2022-09-09 14:22 ` Francesco Dolcini
2022-09-09 14:22 ` Francesco Dolcini
2022-09-22 13:49 ` Ulf Hansson
2022-09-22 13:49 ` Ulf Hansson
2022-09-23 18:00 ` Krzysztof Kozlowski
2022-09-23 18:00 ` Krzysztof Kozlowski
2022-09-26 10:12 ` Ulf Hansson
2022-09-26 10:12 ` Ulf Hansson
2022-09-26 15:11 ` Krzysztof Kozlowski
2022-09-26 15:11 ` Krzysztof Kozlowski
2022-09-27 9:48 ` Ulf Hansson
2022-09-27 9:48 ` Ulf Hansson
2022-09-27 12:49 ` Geert Uytterhoeven
2022-09-27 12:49 ` Geert Uytterhoeven
2022-09-27 14:26 ` Krzysztof Kozlowski
2022-09-27 14:26 ` Krzysztof Kozlowski
2022-09-28 7:59 ` Ulf Hansson
2022-09-28 7:59 ` Ulf Hansson
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=20220609150851.23084-2-max.oss.09@gmail.com \
--to=max.oss.09@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=khilman@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=max.krummenacher@toradex.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.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.