From: Kanishka Chakraborty <kanishka.developer@gmail.com>
To: kamal.wadhwa@oss.qualcomm.com, maulik.shah@oss.qualcomm.com
Cc: broonie@kernel.org, lgirdwood@gmail.com, andersson@kernel.org,
konradybcio@kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/4] regulator: qcom-rpmh: Support RPMH address reads and use it for rpmh-regulators
Date: Fri, 23 Oct 2026 13:18:38 +0530 [thread overview]
Message-ID: <20261023074838.29254-1-kanishka.developer@gmail.com> (raw)
In-Reply-To: <20260801-b4-read-rpmh-v5-v6-0-9fcb54928523@oss.qualcomm.com>
Hi,
with this series in v7.3, SM7150 (Snapdragon 732G, Xiaomi Redmi Note 10
Pro) no longer boots. SM7150 support is not upstream yet; I am running
v7.3 with the sm7150-mainline patches on top, but the problem looks
independent of that and may affect other SoCs with older RSCs.
Symptom: the boot stops around the time the RPMh regulators register.
The display (left on by the bootloader) goes grey at that point and the
initramfs never runs, while the kernel apparently keeps running (the
watchdog keeps being serviced). The v7.1-based sm7150-mainline tree
boots fine on the same device with the same DT.
What I checked:
- Reverting 09d99ff7fc3c ("regulator: qcom-rpmh: readback
voltage/bypass/mode set during bootup") and its follow-up 216e8873bc80
("regulator: qcom-rpmh: Fix coding style issues") makes v7.3 boot.
- A log-only variant that still issues every rpmh_read() but throws the
results away (vreg->mode, bypassed and voltage_selector restored to the
pre-readback defaults) hangs exactly the same way. So issuing the reads
is enough to break it, independent of what is done with the values.
I couldn't capture the per-read log lines: the display dies at that
point and the boot never gets far enough for USB or a log.
- The apps RSC here reports RSC_DRV_ID = 0x00010100, i.e. version 1.1.
rpmh-rsc only describes the v2.7 and v3.0 register layouts and uses the
v2.7 one for everything below 3.0, so on this RSC the read path writes
CMD_MSGID without the write bit and later reads RESP_DATA at the v2.7
offset. This SoC has two active-only TCSes.
I don't know whether read requests are supported on RSC v1.x at all, or
only need a different register layout there. Would it make sense to only
issue reads on RSCs known to support them, and let rpmh_read() return
-EOPNOTSUPP otherwise, so the regulator driver falls back to the old
behaviour?
I'm happy to test patches or collect more data on this device.
Thanks,
Kanishka
prev parent reply other threads:[~2026-10-23 7:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 8:00 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-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 [this message]
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=20261023074838.29254-1-kanishka.developer@gmail.com \
--to=kanishka.developer@gmail.com \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--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=maulik.shah@oss.qualcomm.com \
/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®