From: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
To: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
jens.glathe@oldschoolsolutions.biz,
konrad.dybcio@oss.qualcomm.com
Subject: [RFC PATCH v1 1/2] regulator: Add dummy regulator consumer binding
Date: Sat, 7 Jun 2025 23:25:38 +0200 [thread overview]
Message-ID: <20250607212654.126412-2-alex.vinarskis@gmail.com> (raw)
In-Reply-To: <20250607212654.126412-1-alex.vinarskis@gmail.com>
Add the devicetree binding for the upcoming driver.
Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
---
.../bindings/regulator/dummy-consumer.yaml | 39 +++++++++++++++++++
1 file changed, 39 insertions(+)
create mode 100644 Documentation/devicetree/bindings/regulator/dummy-consumer.yaml
diff --git a/Documentation/devicetree/bindings/regulator/dummy-consumer.yaml b/Documentation/devicetree/bindings/regulator/dummy-consumer.yaml
new file mode 100644
index 000000000000..efe8cccab080
--- /dev/null
+++ b/Documentation/devicetree/bindings/regulator/dummy-consumer.yaml
@@ -0,0 +1,39 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/regulator/dummy-consumer.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Dummy regulator consumer
+
+maintainers:
+ - Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
+
+description: |
+ Simple dummy regulator consumer node for devices which are not/cannot be
+ described in the devicetree, and do not need to be powered on during
+ suspend. A power-friendly alternative to leaving regulator without
+ consumer with 'regulator-always-on' property.
+
+properties:
+ compatible:
+ enum:
+ - regulator-dummy-consumer
+
+ vdd-supply:
+ description: Regulator to control
+ $ref: /schemas/types.yaml#/definitions/phandle
+
+required:
+ - compatible
+ - vdd-supply
+
+additionalProperties: false
+
+examples:
+ - |
+ integrated-usb-camera {
+ compatible = "regulator-dummy-consumer";
+
+ vdd-supply = <&vdd>;
+ };
--
2.45.2
next prev parent reply other threads:[~2025-06-07 21:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 21:25 [RFC PATCH v1 0/2] Introduce dummy regulator consumer Aleksandrs Vinarskis
2025-06-07 21:25 ` Aleksandrs Vinarskis [this message]
2025-06-08 22:33 ` [RFC PATCH v1 1/2] regulator: Add dummy regulator consumer binding Rob Herring (Arm)
2025-06-07 21:25 ` [RFC PATCH v1 2/2] regulator: Introduce dummy regulator consumer driver Aleksandrs Vinarskis
2025-06-08 22:33 ` [RFC PATCH v1 0/2] Introduce dummy regulator consumer Mark Brown
2025-06-09 20:32 ` Aleksandrs Vinarskis
2025-06-09 20:50 ` Mark Brown
2025-06-09 21:15 ` Aleksandrs Vinarskis
2025-06-10 13:51 ` Mark Brown
2025-06-28 6:14 ` Jens Glathe
2025-06-28 14:35 ` Konrad Dybcio
2025-06-30 13:11 ` Mark Brown
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=20250607212654.126412-2-alex.vinarskis@gmail.com \
--to=alex.vinarskis@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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