From: Saikiran <bjsaikiran@gmail.com>
To: broonie@kernel.org, lgirdwood@gmail.com
Cc: andersson@kernel.org, konrad.dybcio@kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
robh@kernel.org, krzk+dt@kernel.org, devicetree@vger.kernel.org,
Saikiran <bjsaikiran@gmail.com>
Subject: [PATCH v3 1/2] dt-bindings: regulator: qcom,rpmh: Allow regulator-off-on-delay-us
Date: Wed, 28 Jan 2026 00:32:10 +0530 [thread overview]
Message-ID: <20260127190211.14312-2-bjsaikiran@gmail.com> (raw)
In-Reply-To: <20260127190211.14312-1-bjsaikiran@gmail.com>
Add the standard 'regulator-off-on-delay-us' property to the list of
allowed properties for RPMh regulators.
This property is required for platforms where specific rails (like camera
LDOs) rely on passive discharge and need a mandatory off-time constraint
enforced by the regulator core.
Signed-off-by: Saikiran <bjsaikiran@gmail.com>
---
.../devicetree/bindings/regulator/qcom,rpmh-regulator.yaml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.yaml b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.yaml
index 58bb0ad5dda4..b02311263191 100644
--- a/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.yaml
+++ b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.yaml
@@ -131,6 +131,8 @@ properties:
$ref: regulator.yaml#
unevaluatedProperties: false
description: BOB regulator node.
+ properties:
+ regulator-off-on-delay-us: true
dependencies:
regulator-allow-set-load: [ regulator-allowed-modes ]
@@ -140,6 +142,8 @@ patternProperties:
$ref: regulator.yaml#
unevaluatedProperties: false
description: smps/ldo regulator nodes(s).
+ properties:
+ regulator-off-on-delay-us: true
dependencies:
regulator-allow-set-load: [ regulator-allowed-modes ]
--
2.51.0
next prev parent reply other threads:[~2026-01-27 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 19:02 [PATCH v3 0/2] regulator: qcom-rpmh: Add off-on-delay support Saikiran
2026-01-27 19:02 ` Saikiran [this message]
2026-01-29 17:49 ` [PATCH v3 1/2] dt-bindings: regulator: qcom,rpmh: Allow regulator-off-on-delay-us Rob Herring
2026-01-29 18:15 ` Mark Brown
2026-01-30 11:05 ` Konrad Dybcio
2026-02-03 16:20 ` Kamal Wadhwa
2026-02-03 16:30 ` Mark Brown
2026-02-06 16:19 ` Kamal Wadhwa
2026-02-08 13:07 ` Saikiran B
2026-02-12 8:51 ` Kamal Wadhwa
2026-01-27 19:02 ` [PATCH v3 2/2] regulator: qcom-rpmh: Add support for regulator-off-on-delay-us Saikiran
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=20260127190211.14312-2-bjsaikiran@gmail.com \
--to=bjsaikiran@gmail.com \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--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