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 2/2] regulator: qcom-rpmh: Add support for regulator-off-on-delay-us
Date: Wed, 28 Jan 2026 00:32:11 +0530 [thread overview]
Message-ID: <20260127190211.14312-3-bjsaikiran@gmail.com> (raw)
In-Reply-To: <20260127190211.14312-1-bjsaikiran@gmail.com>
The core regulator framework supports enforcing a physical off-time via
standard properties, but the `qcom-rpmh-regulator` driver currently ignores
them.
The issue is platform-specific: The Lenovo Yoga Slim 7x (Snapdragon X Elite)
has large bulk capacitors on the camera rails (LDO1, LDO3, LDO7). When these
regulators are disabled, the voltage decays very slowly (passive discharge).
If the rail is re-enabled before this discharge completes, the sensor
experiences a brownout and fails to initialize.
Add support for parsing the 'regulator-off-on-delay-us' property from
the device tree to enforce this physical constraint.
Signed-off-by: Saikiran <bjsaikiran@gmail.com>
---
drivers/regulator/qcom-rpmh-regulator.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/regulator/qcom-rpmh-regulator.c b/drivers/regulator/qcom-rpmh-regulator.c
index 6e4cb2871fca..aafba61551b3 100644
--- a/drivers/regulator/qcom-rpmh-regulator.c
+++ b/drivers/regulator/qcom-rpmh-regulator.c
@@ -503,6 +503,9 @@ static int rpmh_regulator_init_vreg(struct rpmh_vreg *vreg, struct device *dev,
vreg->always_wait_for_ack = of_property_read_bool(node,
"qcom,always-wait-for-ack");
+ of_property_read_u32(node, "regulator-off-on-delay-us",
+ &vreg->rdesc.off_on_delay);
+
vreg->rdesc.owner = THIS_MODULE;
vreg->rdesc.type = REGULATOR_VOLTAGE;
vreg->rdesc.ops = vreg->hw_data->ops;
--
2.51.0
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 ` [PATCH v3 1/2] dt-bindings: regulator: qcom,rpmh: Allow regulator-off-on-delay-us Saikiran
2026-01-29 17:49 ` 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 ` Saikiran [this message]
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-3-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