From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Vinod Koul <vkoul@kernel.org>, Mark Brown <broonie@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
David Collins <collinsd@codeaurora.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] regulator: qcom-rpmh: Add support for PM8450 regulators
Date: Wed, 1 Dec 2021 15:11:57 +0300 [thread overview]
Message-ID: <fb4ee07b-6e91-9b74-26b4-e0368899bc20@linaro.org> (raw)
In-Reply-To: <20211201072515.3968843-3-vkoul@kernel.org>
On 01/12/2021 10:25, Vinod Koul wrote:
> Add the rpmh regulators found in PM8450 PMIC
>
> Signed-off-by: Vinod Koul <vkoul@kernel.org>
Tested-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/regulator/qcom-rpmh-regulator.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/drivers/regulator/qcom-rpmh-regulator.c b/drivers/regulator/qcom-rpmh-regulator.c
> index 12425f667c00..cea6d7413864 100644
> --- a/drivers/regulator/qcom-rpmh-regulator.c
> +++ b/drivers/regulator/qcom-rpmh-regulator.c
> @@ -969,6 +969,20 @@ static const struct rpmh_vreg_init_data pm8350c_vreg_data[] = {
> {}
> };
>
> +static const struct rpmh_vreg_init_data pm8450_vreg_data[] = {
> + RPMH_VREG("smps1", "smp%s1", &pmic5_ftsmps520, "vdd-s1"),
> + RPMH_VREG("smps2", "smp%s2", &pmic5_ftsmps520, "vdd-s2"),
> + RPMH_VREG("smps3", "smp%s3", &pmic5_ftsmps520, "vdd-s3"),
> + RPMH_VREG("smps4", "smp%s4", &pmic5_ftsmps520, "vdd-s4"),
> + RPMH_VREG("smps5", "smp%s5", &pmic5_ftsmps520, "vdd-s5"),
> + RPMH_VREG("smps6", "smp%s6", &pmic5_ftsmps520, "vdd-s6"),
> + RPMH_VREG("ldo1", "ldo%s1", &pmic5_nldo, "vdd-l1"),
> + RPMH_VREG("ldo2", "ldo%s2", &pmic5_nldo, "vdd-l2"),
> + RPMH_VREG("ldo3", "ldo%s3", &pmic5_nldo, "vdd-l3"),
> + RPMH_VREG("ldo4", "ldo%s4", &pmic5_pldo_lv, "vdd-l4"),
> + {}
> +};
> +
> static const struct rpmh_vreg_init_data pm8009_vreg_data[] = {
> RPMH_VREG("smps1", "smp%s1", &pmic5_hfsmps510, "vdd-s1"),
> RPMH_VREG("smps2", "smp%s2", &pmic5_hfsmps515, "vdd-s2"),
> @@ -1213,6 +1227,10 @@ static const struct of_device_id __maybe_unused rpmh_regulator_match_table[] = {
> .compatible = "qcom,pm8350c-rpmh-regulators",
> .data = pm8350c_vreg_data,
> },
> + {
> + .compatible = "qcom,pm8450-rpmh-regulators",
> + .data = pm8450_vreg_data,
> + },
> {
> .compatible = "qcom,pm8998-rpmh-regulators",
> .data = pm8998_vreg_data,
>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2021-12-01 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 7:25 [PATCH 0/2] regulator: qcom,rpmh: Add support for PM8450 Vinod Koul
2021-12-01 7:25 ` [PATCH 1/2] regulator: qcom,rpmh: Add compatible " Vinod Koul
2021-12-01 7:25 ` [PATCH 2/2] regulator: qcom-rpmh: Add support for PM8450 regulators Vinod Koul
2021-12-01 12:11 ` Dmitry Baryshkov [this message]
2021-12-01 18:32 ` [PATCH 0/2] regulator: qcom,rpmh: Add support for PM8450 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=fb4ee07b-6e91-9b74-26b4-e0368899bc20@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=collinsd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).