Skip to contentSkip to conversation

regulator: qcom,rpmh: Add support for PM8450

PATCH In review Vinod Koul 3 participants 5 messages Dec 1, 2021

Subsystems (3)
lore
Share & tools
lore

Vinod Koul

author
#0 lore raw

cover regulator: qcom,rpmh: Add support for PM8450

This add the binding and driver update to support the PM8450 which is found in SM8450 platform

Vinod Koul (2):
regulator: qcom,rpmh: Add compatible for PM8450
regulator: qcom-rpmh: Add support for PM8450 regulators

 .../regulator/qcom,rpmh-regulator.yaml         |  2 ++
 drivers/regulator/qcom-rpmh-regulator.c        | 18 ++++++++++++++++++
 2 files changed, 20 insertions(+)
Signature · 1 line
2.31.1
author
#1 lore raw

PATCH 1/2 regulator: qcom,rpmh: Add compatible for PM8450

Add compatible string for PM8450 used in SM8450 boards.

---
 .../devicetree/bindings/regulator/qcom,rpmh-regulator.yaml      | 2 ++
 1 file changed, 2 insertions(+)
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.yaml +2 -0
index b959504e0ea4..6c04f256d497 100644
@@ -43,6 +43,7 @@ description: |
       For PM8150L, smps1 - smps8, ldo1 - ldo11, bob, flash, rgb
       For PM8350, smps1 - smps12, ldo1 - ldo10
       For PM8350C, smps1 - smps10, ldo1 - ldo13, bob
+      For PM8450, smps1 - smps6, ldo1 - ldo4
       For PM8998, smps1 - smps13, ldo1 - ldo28, lvs1 - lvs2
       For PMI8998, bob
       For PMR735A, smps1 - smps3, ldo1 - ldo7
@@ -62,6 +63,7 @@ properties:
       - qcom,pm8150l-rpmh-regulators
       - qcom,pm8350-rpmh-regulators
       - qcom,pm8350c-rpmh-regulators
+      - qcom,pm8450-rpmh-regulators
       - qcom,pm8998-rpmh-regulators
       - qcom,pmi8998-rpmh-regulators
       - qcom,pmm8155au-rpmh-regulators
Signature · 1 line
2.31.1
author
#2 lore raw

PATCH 2/2 regulator: qcom-rpmh: Add support for PM8450 regulators

In reply to Vinod Koul

Add the rpmh regulators found in PM8450 PMIC

---
 drivers/regulator/qcom-rpmh-regulator.c | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
drivers/regulator/qcom-rpmh-regulator.c +18 -0
index 12425f667c00..cea6d7413864 100644
@@ -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,
Signature · 1 line
2.31.1
Tested-by on v1 2/2
#3 lore raw

Re: [PATCH 2/2] regulator: qcom-rpmh: Add support for PM8450 regulators

Quoted 3 lines · Vinod Koul

Add the rpmh regulators found in PM8450 PMIC

Quoted 41 lines
---
  drivers/regulator/qcom-rpmh-regulator.c | 18 ++++++++++++++++++
  1 file changed, 18 insertions(+)
drivers/regulator/qcom-rpmh-regulator.c +18 -0
index 12425f667c00..cea6d7413864 100644
@@ -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,
Signature · 2 lines
With best wishes
Dmitry
maintainer
#4 lore raw
In reply to Vinod Koul
Quoted 8 lines · Vinod Koul

This add the binding and driver update to support the PM8450 which is found in SM8450 platform

Vinod Koul (2):
regulator: qcom,rpmh: Add compatible for PM8450
regulator: qcom-rpmh: Add support for PM8450 regulators

[...]

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/2] regulator: qcom,rpmh: Add compatible for PM8450

      commit: fa3b06f59a03a3a4639755478e0cf5b508a1b454
[2/2] regulator: qcom-rpmh: Add support for PM8450 regulators
      commit: d69e19723f88a3ba6d4e0e52f51dd4c59cc2ae93

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark