From: kholk11@gmail.com
To: linux-arm-msm@vger.kernel.org
Cc: kholk11@gmail.com, marijns95@gmail.com, broonie@kernel.org,
lgirdwood@gmail.com, mark.rutland@arm.com, robh+dt@kernel.org,
lee.jones@linaro.org, agross@kernel.org
Subject: [PATCH 1/5] qcom: spmi-regulator: Add support for ULT LV_P50 and ULT P300
Date: Sat, 21 Sep 2019 11:50:39 +0200 [thread overview]
Message-ID: <20190921095043.62593-2-kholk11@gmail.com> (raw)
In-Reply-To: <20190921095043.62593-1-kholk11@gmail.com>
From: "Angelo G. Del Regno" <kholk11@gmail.com>
The ULT LV_P50 shares the same configuration as the other ULT LV_Pxxx
and the ULT P300 shares the same as the other ULT Pxxx.
These two regulator types are found on PM8950 and its variants.
Signed-off-by: Angelo G. Del Regno <kholk11@gmail.com>
---
drivers/regulator/qcom_spmi-regulator.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/regulator/qcom_spmi-regulator.c b/drivers/regulator/qcom_spmi-regulator.c
index 7f51c5fc8194..5a269ec46963 100644
--- a/drivers/regulator/qcom_spmi-regulator.c
+++ b/drivers/regulator/qcom_spmi-regulator.c
@@ -1466,10 +1466,12 @@ static const struct spmi_regulator_mapping supported_regulators[] = {
SPMI_VREG(ULT_LDO, N600_ST, 0, INF, ULT_LDO, ult_ldo, ult_nldo, 10000),
SPMI_VREG(ULT_LDO, N900_ST, 0, INF, ULT_LDO, ult_ldo, ult_nldo, 10000),
SPMI_VREG(ULT_LDO, N1200_ST, 0, INF, ULT_LDO, ult_ldo, ult_nldo, 10000),
+ SPMI_VREG(ULT_LDO, LV_P50, 0, INF, ULT_LDO, ult_ldo, ult_pldo, 10000),
SPMI_VREG(ULT_LDO, LV_P150, 0, INF, ULT_LDO, ult_ldo, ult_pldo, 10000),
SPMI_VREG(ULT_LDO, LV_P300, 0, INF, ULT_LDO, ult_ldo, ult_pldo, 10000),
SPMI_VREG(ULT_LDO, LV_P450, 0, INF, ULT_LDO, ult_ldo, ult_pldo, 10000),
SPMI_VREG(ULT_LDO, P600, 0, INF, ULT_LDO, ult_ldo, ult_pldo, 10000),
+ SPMI_VREG(ULT_LDO, P300, 0, INF, ULT_LDO, ult_ldo, ult_pldo, 10000),
SPMI_VREG(ULT_LDO, P150, 0, INF, ULT_LDO, ult_ldo, ult_pldo, 10000),
SPMI_VREG(ULT_LDO, P50, 0, INF, ULT_LDO, ult_ldo, ult_pldo, 5000),
};
--
2.21.0
next prev parent reply other threads:[~2019-09-21 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 9:50 [PATCH 0/5] Add support for PM8950/PMI8950/PM8004 regulators kholk11
2019-09-21 9:50 ` kholk11 [this message]
2019-09-21 9:50 ` [PATCH 2/5] regulator: qcom_spmi: Add PM8950 SPMI regulator kholk11
2019-09-21 9:50 ` [PATCH 3/5] regulator: qcom_smd: Add PM8950 regulators kholk11
2019-09-21 9:50 ` [PATCH 4/5] mfd: qcom-spmi-pmic: Add support for PM/PMI8950 kholk11
2019-10-04 14:27 ` Lee Jones
2019-09-21 9:50 ` [PATCH 5/5] regulator: qcom_spmi: Add support for PM8004 regulators kholk11
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=20190921095043.62593-2-kholk11@gmail.com \
--to=kholk11@gmail.com \
--cc=agross@kernel.org \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marijns95@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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