From: Val Packett <val@packett.cool>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
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: Sun, 15 Nov 2026 17:05:46 -0300 [thread overview]
Message-ID: <d8415f6d-3324-4e3a-905b-7ea8c39bd2c4@packett.cool> (raw)
In-Reply-To: <648ae82b-edda-42e1-b5b2-522a791d6bdb@packett.cool>
On 11/4/26 7:15 PM, Val Packett wrote:
> Hi,
>
> On 9/8/26 4:46 AM, Konrad Dybcio wrote:
>> [..]
>>> 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
>
> This happens with some LDOs on sc8180x as well…
>
> I've been getting the "failed to read VOLTAGE ret = -110" error when
> enabling the L14A LDO (for cameras on the Surface Pro X). (And that
> breaks the entire boot)
>
> With the "Skip read requests on unsupported platforms" patch, instead
> of that I get an error exactly like this one above, when it's being
> set to high power mode.
>
> Even patching out the *writes* to mode/voltage specifically for ldo14,
> rpmh_regulator_set_enable_state on ldo14 crashes/stalls aoss (and at
> least in some dt configurations, boot proceeds but wifi/usb break) :(
>
> But S5A, L7A, L9A, L12A were listed there normally from the start and
> never had this issue. S5A here did not have an issue even with the
> read code enabled.
..So apparently, the "weird" LDOs work when controlled directly
over SPMI, rather than by talking to AOSS:
https://github.com/linux-surface/surface-pro-x/issues/55#issuecomment-6872761348
They have a very different address in cmd-db than the AOSS-owned ones.
Now the question is, is this 8180 specific or is it exactly the same on
8150?
> ~val
next prev parent reply other threads:[~2026-11-15 20:05 UTC|newest]
Thread overview: 15+ 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
2026-11-04 22:15 ` Val Packett
2026-11-15 20:05 ` Val Packett [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
2026-10-23 7:48 ` Kanishka Chakraborty
2026-10-26 21:21 ` 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=d8415f6d-3324-4e3a-905b-7ea8c39bd2c4@packett.cool \
--to=val@packett.cool \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=kamal.wadhwa@oss.qualcomm.com \
--cc=konrad.dybcio@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®