From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Jishnu Prakash <jishnu.prakash@oss.qualcomm.com>,
Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
Cc: Saikiran <bjsaikiran@gmail.com>,
lgirdwood@gmail.com, andersson@kernel.org,
konradybcio@kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: regulator: qcom,rpmh: Allow regulator-off-on-delay-us
Date: Fri, 30 Jan 2026 12:05:38 +0100 [thread overview]
Message-ID: <fa760b2f-4b8c-46d5-90b9-2ad9e69ebf04@oss.qualcomm.com> (raw)
In-Reply-To: <355213ef-106c-4383-88e7-9b40f5b1c1ef@sirena.org.uk>
On 1/29/26 7:15 PM, Mark Brown wrote:
> On Thu, Jan 29, 2026 at 11:49:42AM -0600, Rob Herring wrote:
>> On Wed, Jan 28, 2026 at 12:32:10AM +0530, Saikiran wrote:
>
>>> 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.
>
>> Does enforcing some off time on all your regulators cause some negative
>> impact on the ones that don't need it? If turning them back on is
>> performance critical maybe don't turn them off in the first place.
>
> You might see something like unexpectedly long delays resuming a runtime
> suspended device. Generally I'd say that if the delays needed for
> something like this are long enough for anyone to notice they're long
> enough to be disruptive.
>
> Having said that I believe an active discharge feature in the hardware
> has been identified and is being investigated, that's generally a vastly
> better solution all round so hopefully this change isn't needed at all.
+Jishnu, Kamal
Could you please confirm whether our hw can do that?
Konrad
next prev parent reply other threads:[~2026-01-30 11:05 UTC|newest]
Thread overview: 12+ 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 [this message]
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
2026-05-15 11:16 ` [PATCH v3 0/2] regulator: qcom-rpmh: Add off-on-delay support Kamal Wadhwa
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=fa760b2f-4b8c-46d5-90b9-2ad9e69ebf04@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bjsaikiran@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jishnu.prakash@oss.qualcomm.com \
--cc=kamal.wadhwa@oss.qualcomm.com \
--cc=konradybcio@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