From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Shawn Guo <shengchao.guo@oss.qualcomm.com>,
Mark Brown <broonie@kernel.org>
Cc: 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: Mon, 20 Apr 2026 11:21:23 +0200 [thread overview]
Message-ID: <77a87de7-3c66-44b5-9900-df8798d3074f@oss.qualcomm.com> (raw)
In-Reply-To: <20260420072639.1249984-3-shengchao.guo@oss.qualcomm.com>
On 4/20/26 9:26 AM, Shawn Guo wrote:
> From: Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
>
> Add support for PMAU0102 PMIC voltage regulators which are present on
> Nord boards.
>
> Signed-off-by: Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
> Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com>
> ---
> drivers/regulator/qcom-rpmh-regulator.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/regulator/qcom-rpmh-regulator.c b/drivers/regulator/qcom-rpmh-regulator.c
> index 6e4cb2871fca..9545300d7b03 100644
> --- a/drivers/regulator/qcom-rpmh-regulator.c
> +++ b/drivers/regulator/qcom-rpmh-regulator.c
> @@ -1100,6 +1100,21 @@ static const struct rpmh_vreg_init_data pm8998_vreg_data[] = {
> {}
> };
>
> +static const struct rpmh_vreg_init_data pmau0102_vreg_data[] = {
> + RPMH_VREG("smps1", SMPS, 1, &pmic5_ftsmps527, "vdd-s1"),
> + RPMH_VREG("smps2", SMPS, 2, &pmic5_ftsmps527, "vdd-s2"),
> + RPMH_VREG("smps3", SMPS, 3, &pmic5_ftsmps527, "vdd-s3"),
> + RPMH_VREG("smps4", SMPS, 4, &pmic5_ftsmps527, "vdd-s4"),
> + RPMH_VREG("smps5", SMPS, 5, &pmic5_ftsmps527, "vdd-s5"),
> + RPMH_VREG("smps6", SMPS, 6, &pmic5_ftsmps527, "vdd-s6"),
> + RPMH_VREG("smps7", SMPS, 7, &pmic5_ftsmps527, "vdd-s7"),
> + RPMH_VREG("smps8", SMPS, 8, &pmic5_ftsmps527, "vdd-s8"),
> + RPMH_VREG("ldo1", LDO, 1, &pmic5_nldo515, NULL),
> + RPMH_VREG("ldo2", LDO, 2, &pmic5_nldo515, NULL),
> + RPMH_VREG("ldo3", LDO, 3, &pmic5_pldo515_mv, NULL),
Any reason for the NULL supplies?
Konrad
next prev parent reply other threads:[~2026-04-20 9:21 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 [this message]
2026-04-21 12:54 ` Shawn Guo
2026-04-22 0:56 ` Dmitry Baryshkov
2026-04-22 2:25 ` Shawn Guo
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=77a87de7-3c66-44b5-9900-df8798d3074f@oss.qualcomm.com \
--to=konrad.dybcio@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=kamal.wadhwa@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 \
--cc=shengchao.guo@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