From: Mark Brown <broonie@kernel.org>
To: Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
robh@kernel.org, Saikiran <bjsaikiran@gmail.com>,
monish.chunara@oss.qualcomm.com, jishnu.prakash@oss.qualcomm.com,
nitin.rawat@oss.qualcomm.com,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
lgirdwood@gmail.com, andersson@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 0/2] regulator: qcom-rpmh: Add off-on-delay support
Date: Mon, 14 Sep 2026 19:34:13 +0100 [thread overview]
Message-ID: <aqg-JSTrbg-xR69l@sirena.org.uk> (raw)
In-Reply-To: <xmjovrqonged7m77zlx4gbz6xvfksygbw7g4vgv2stlucvqoy6@uie3qdhdtkoe>
[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]
On Wed, Sep 09, 2026 at 02:34:21AM +0530, Kamal Wadhwa wrote:
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
> However recently on Qualcomm's QCS8300 RB4 boards we started seeing "NOP OUT" issue
> for UFS driver, where this patch seems to be helping.
> Also, Rob had earlier raised a few points to Saikiran on this patch series
> (https://lore.kernel.org/all/20260129174829.GA1324020-robh@kernel.org/):
> 3. If we can avoid turning the regulator off itself, so we may not need this delay
> point 3 - We evaluated this for UFS - but the problem is that the issue happens in
> the defer probe path, so if we avoid turning off the regulator, it leads to long
> error prints appearing for the regulator being left ON. So we couldn't take that
> path.
I think Rob might be thinking here of something like the runtime PM
autosuspend delay where once the final reference is dropped we wait some
time before we actually implement the power off in hardware, thus a
quick power cycle would never actually get implemented. That does sound
like a good idea if we've got issues with quick cycling, obviously the
actual delay would still be needed but if you've got quick bounces
happening routinely then a delay like that would allow you to avoid both
power off and ramp delays.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-14 18:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 19:02 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 ` [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
2026-06-16 11:48 ` Konrad Dybcio
2026-06-24 22:16 ` Kamal Wadhwa
2026-06-29 12:13 ` Konrad Dybcio
2026-09-08 13:13 ` Kamal Wadhwa
2026-09-08 13:26 ` Mark Brown
2026-09-08 21:04 ` Kamal Wadhwa
2026-09-14 18:34 ` Mark Brown [this message]
2026-09-16 8:05 ` Jishnu Prakash
2026-09-16 11:57 ` Mark Brown
2026-06-30 14:11 ` Manivannan Sadhasivam
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=aqg-JSTrbg-xR69l@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andersson@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=bjsaikiran@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jishnu.prakash@oss.qualcomm.com \
--cc=kamal.wadhwa@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monish.chunara@oss.qualcomm.com \
--cc=nitin.rawat@oss.qualcomm.com \
--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
all inboxes | Powered by JetHome®