From: Saikiran <bjsaikiran@gmail.com>
To: broonie@kernel.org
Cc: andersson@kernel.org, konrad.dybcio@linaro.org,
lgirdwood@gmail.com, linux-regulator@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] regulator: qcom-rpmh: Add support for regulator-off-on-delay-us
Date: Tue, 27 Jan 2026 22:55:21 +0530 [thread overview]
Message-ID: <20260127172522.73135-1-bjsaikiran@gmail.com> (raw)
This patch adds support for the generic `regulator-off-on-delay-us` property
to the Qualcomm RPMh regulator driver.
The core regulator framework supports enforcing a physical off-time via
standard properties, but the `qcom-rpmh-regulator` driver currently ignores
them. This prevents boards with slow-discharging rails from enforcing safe
power-cycling constraints.
Motivation / Test Result:
On the Lenovo Yoga Slim 7x (Snapdragon X Elite), the camera regulators
rely on passive discharge and require a significant off-time to drop below
brownout thresholds.
I have tested this patch on the Yoga Slim 7x. When the delay property is
present in the device tree, the regulator core correctly blocks re-enable
calls until the delay passes. This successfully fixes the camera brownout
issues and allows reliable sensor initialization during rapid power cycling.
I am submitting this driver support first to ensure the mechanism is available.
Once the consumer nodes (camera) for this board are upstream, we will apply
the specific delay values in the DTS.
Saikiran (1):
regulator: qcom-rpmh: Add support for regulator-off-on-delay-us
next reply other threads:[~2026-01-27 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 17:25 Saikiran [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-27 17:27 [PATCH] regulator: qcom-rpmh: Add support for regulator-off-on-delay-us Saikiran
2026-01-27 17:27 ` Saikiran
2026-01-27 17:35 ` Mark Brown
2026-01-27 17:43 ` Saikiran B
2026-01-27 17:50 ` Mark Brown
2026-01-27 17:28 ` 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=20260127172522.73135-1-bjsaikiran@gmail.com \
--to=bjsaikiran@gmail.com \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-regulator@vger.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