From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Vinod Koul <vkoul@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v6 3/4] regulator: qcom-rpmh: readback voltage/bypass/mode set during bootup
Date: Tue, 8 Sep 2026 09:46:02 +0200 [thread overview]
Message-ID: <14bb6196-8274-4c94-922e-4ec8e2d7f2e5@oss.qualcomm.com> (raw)
In-Reply-To: <5b2yo644hjtnyue42da6zltxpai2hlod3verxbkecbmmaw2ktj@6qhufjoik7kw>
On 9/7/26 2:59 PM, Kamal Wadhwa wrote:
> On Tue, Sep 01, 2026 at 11:49:42AM +0200, Konrad Dybcio wrote:
>> On 8/1/26 10:00 AM, Kamal Wadhwa wrote:
>>> Currently, during regulator registration, regulator framework sends an
>>> unnecessary `min-microvolts` request for the rpmh-regulator device. This
>>> happens because in current design, we do not have a way to readback the
>>> voltage settings that was set during the bootloader stage.
>>>
>>> Fix this by using the rpmh_read() API to read the regulator voltage
>>> settings done during boot and make it available to regulator framework
>>> from the very first read after the bootup.
>>>
>>> Also use this API to read the mode/bypass settings as well. This will
>>> provide the regulator framework a sense of the initial settings done by
>>> bootloader and thus preventing any redundant writes for any setting post
>>> bootup incase the same setting was already applied during bootup.
>>>
>>> Signed-off-by: Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
>>> ---
>>
>> SC8180X Primus hangs with this patch applied and so does SM8150 HDK.
>
> Ok, i did see some issues on SM8550 but those were mainly related to the
> voltage range check leading to some regulator failing to probe, for that
> this below change may help.
> https://lore.kernel.org/all/20260720-b4-regulator-core-clamp-voltage-v1-1-8e5eec076a8e@oss.qualcomm.com/
>
> But i suppose you may already have it?
Yes
> do you see the problem with the rpmh_read() or in the voltage range check?
Applying
20260812-rpmh-timeout-debug-v1-v3-0-68c0a40dce23@oss.qualcomm.com
I get:
[ 12.735771] qcom_rpmh RSC:apps_rsc
[ 12.739294] qcom_rpmh Request: tcs-in-use:YES state=2 wait_for_compl=1
[ 12.749622] qcom_rpmh TCS=0 [ctrlr-sts:BUSY amc-mode:0x1010000 irq-sts:WAITING]
[ 12.763769] qcom_rpmh CMD=0 [addr=0x43100(VRM/smpc8) data=0x7 resp-required sts=triggered+sent-to-aoss]
[ 12.781024] qcom_rpmh Request: tcs-in-use:YES state=2 wait_for_compl=1
[ 12.797493] qcom_rpmh TCS=1 [ctrlr-sts:BUSY amc-mode:0x1010000 irq-sts:WAITING]
[ 12.811733] qcom_rpmh CMD=0 [addr=0x40000(VRM/smpa5) data=0x0 resp-required sts=triggered+sent-to-aoss]
[ 12.829006] qcom_rpmh HW IRQ 37 is NOT PENDING at GIC
[ 12.843942] qcom_rpmh Completion is not done
[ 12.853536] qcom_rpmh ERROR: Accelerator(s) at AOSS did not respond
Neither S8C nor S5A are "special", neither of them feeds an
ARC resource (at a glance, anyway)
so it's the read part,
RPMH_REGULATOR_REG_VRM_VOLTAGE and RPMH_REGULATOR_REG_VRM_MODE stall
RPMH_REGULATOR_REG_ENABLE interestingly doesn't
Konrad
next prev parent reply other threads:[~2026-09-08 7:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 8:00 [PATCH v6 0/4] regulator: qcom-rpmh: Support RPMH address reads and use it for rpmh-regulators Kamal Wadhwa
2026-08-01 8:00 ` [PATCH v6 1/4] soc: qcom: rpmh: Add support to read back resource settings Kamal Wadhwa
2026-08-01 8:00 ` [PATCH v6 2/4] regulator: qcom-rpmh: Fix PMIC5 BOB bypass mode handling Kamal Wadhwa
2026-08-01 8:00 ` [PATCH v6 3/4] regulator: qcom-rpmh: readback voltage/bypass/mode set during bootup Kamal Wadhwa
2026-09-01 9:49 ` Konrad Dybcio
2026-09-07 12:59 ` Kamal Wadhwa
2026-09-08 7:46 ` Konrad Dybcio [this message]
2026-09-20 15:45 ` Dmitry Baryshkov
2026-09-20 19:49 ` Kamal Wadhwa
2026-08-01 8:00 ` [PATCH v6 4/4] regulator: qcom-rpmh: Fix coding style issues Kamal Wadhwa
2026-08-07 14:28 ` [PATCH v6 0/4] regulator: qcom-rpmh: Support RPMH address reads and use it for rpmh-regulators 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=14bb6196-8274-4c94-922e-4ec8e2d7f2e5@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=kamal.wadhwa@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@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®