From: Daniel Okazaki <dtokazaki@google.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Zev Weiss <zev@bewilderbeest.net>
Cc: Daniel Okazaki <dtokazaki@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH v1 1/2] regulator: Add regulator-output is_shared property
Date: Wed, 28 May 2025 17:44:24 +0000 [thread overview]
Message-ID: <20250528174426.3318110-2-dtokazaki@google.com> (raw)
In-Reply-To: <20250528174426.3318110-1-dtokazaki@google.com>
The existence of this flag removes the exclusive requirement
for the supply.
Signed-off-by: Daniel Okazaki <dtokazaki@google.com>
---
.../devicetree/bindings/regulator/regulator-output.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/regulator/regulator-output.yaml b/Documentation/devicetree/bindings/regulator/regulator-output.yaml
index 078b37a1a71a..9bc4c68b9978 100644
--- a/Documentation/devicetree/bindings/regulator/regulator-output.yaml
+++ b/Documentation/devicetree/bindings/regulator/regulator-output.yaml
@@ -25,6 +25,11 @@ properties:
description:
Phandle of the regulator supplying the output.
+ is_shared:
+ description:
+ Indicates that the regulator is shared and should not take exclusive control.
+ type: boolean
+
required:
- compatible
- vout-supply
--
2.49.0.1204.g71687c7c1d-goog
next prev parent reply other threads:[~2025-05-28 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 17:44 [PATCH v1 0/2] userspace-consumer: adding is_shared flag Daniel Okazaki
2025-05-28 17:44 ` Daniel Okazaki [this message]
2025-05-28 17:44 ` [PATCH v1 2/2] regulator: userspace-consumer add shared supply functionality Daniel Okazaki
2025-05-28 18:16 ` [PATCH v1 0/2] userspace-consumer: adding is_shared flag Mark Brown
2025-05-28 18:32 ` Daniel Okazaki
2025-05-28 19:20 ` Mark Brown
2025-05-28 21:15 ` Daniel Okazaki
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=20250528174426.3318110-2-dtokazaki@google.com \
--to=dtokazaki@google.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=zev@bewilderbeest.net \
/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
all inboxes | Powered by JetHome®