From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] regulator: rpmh-regulator: Add RPMH regulator support for Nord
Date: Wed, 22 Apr 2026 10:25:03 +0800 [thread overview]
Message-ID: <aegxfxPKE0CGnwqU@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <pakludkmnvnvywmnn4dzl5j6euba3yjgy4zcmpmtmuxjvpg3so@arobndaolbpw>
On Wed, Apr 22, 2026 at 03:56:20AM +0300, Dmitry Baryshkov wrote:
> On Tue, Apr 21, 2026 at 08:54:06PM +0800, Shawn Guo wrote:
...
> > We thought it's fine to not model LDO supplies, as they may not always
> > follow PMIC. But that might be even a good reason for modeling, so that
> > we can have a better DT description for the supplies. I will change it
> > to:
> >
> > RPMH_VREG("ldo1", LDO, 1, &pmic5_nldo515, "vdd-l1"),
> > RPMH_VREG("ldo2", LDO, 2, &pmic5_nldo515, "vdd-l2"),
> > RPMH_VREG("ldo3", LDO, 3, &pmic5_pldo515_mv, "vdd-l3"),
>
> Are those the actual supply pins?
From what I can see from schematics, yes, those are supply pins.
Shawn
prev parent reply other threads:[~2026-04-22 2:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 7:26 [PATCH 0/2] Add PMAU0102 RPMH regulator support Shawn Guo
2026-04-20 7:26 ` [PATCH 1/2] regulator: dt-bindings: qcom,rpmh: Add PMAU0102 support Shawn Guo
2026-04-20 7:26 ` [PATCH 2/2] regulator: rpmh-regulator: Add RPMH regulator support for Nord Shawn Guo
2026-04-20 9:21 ` Konrad Dybcio
2026-04-21 12:54 ` Shawn Guo
2026-04-22 0:56 ` Dmitry Baryshkov
2026-04-22 2:25 ` Shawn Guo [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=aegxfxPKE0CGnwqU@QCOM-aGQu4IUr3Y \
--to=shengchao.guo@oss.qualcomm.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=deepti.jaggi@oss.qualcomm.com \
--cc=devicetree@vger.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=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@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