linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Marko <robimarko@gmail.com>
To: agross@kernel.org, bjorn.andersson@linaro.org,
	konrad.dybcio@somainline.org, lee.jones@linaro.org,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	linus.walleij@linaro.org, lgirdwood@gmail.com,
	broonie@kernel.org, jic23@kernel.org, lars@metafoo.de,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-iio@vger.kernel.org
Cc: Robert Marko <robimarko@gmail.com>
Subject: [PATCH v6 05/12] regulator: qcom_spmi: add support for HT_P600
Date: Mon,  4 Jul 2022 23:23:55 +0200	[thread overview]
Message-ID: <20220704212402.1715182-5-robimarko@gmail.com> (raw)
In-Reply-To: <20220704212402.1715182-1-robimarko@gmail.com>

HT_P600 is a LDO PMOS regulator based on LV P600 using HFS430 layout
found in PMP8074 and PMS405 PMIC-s.

Both PMP8074 and PMS405 define the programmable range as 1.704 to 1.896V
but the actual MAX output voltage depends on the exact LDO in each of
the PMIC-s.
Their usual voltage that they are used is 1.8V.

It has a max current of 600mA, voltage step of 8mV.

Signed-off-by: Robert Marko <robimarko@gmail.com>
---
 drivers/regulator/qcom_spmi-regulator.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/regulator/qcom_spmi-regulator.c b/drivers/regulator/qcom_spmi-regulator.c
index 38bbc70241ae..ad9ad9f4be8e 100644
--- a/drivers/regulator/qcom_spmi-regulator.c
+++ b/drivers/regulator/qcom_spmi-regulator.c
@@ -165,6 +165,7 @@ enum spmi_regulator_subtype {
 	SPMI_REGULATOR_SUBTYPE_ULT_HF_CTL4	= 0x10,
 	SPMI_REGULATOR_SUBTYPE_HFS430		= 0x0a,
 	SPMI_REGULATOR_SUBTYPE_HT_P150		= 0x35,
+	SPMI_REGULATOR_SUBTYPE_HT_P600		= 0x3d,
 };
 
 enum spmi_common_regulator_registers {
@@ -549,6 +550,10 @@ static struct spmi_voltage_range ht_p150_ranges[] = {
 	SPMI_VOLTAGE_RANGE(0, 1616000, 1616000, 3304000, 3304000, 8000),
 };
 
+static struct spmi_voltage_range ht_p600_ranges[] = {
+	SPMI_VOLTAGE_RANGE(0, 1704000, 1704000, 1896000, 1896000, 8000),
+};
+
 static DEFINE_SPMI_SET_POINTS(pldo);
 static DEFINE_SPMI_SET_POINTS(nldo1);
 static DEFINE_SPMI_SET_POINTS(nldo2);
@@ -570,6 +575,7 @@ static DEFINE_SPMI_SET_POINTS(ht_lvpldo);
 static DEFINE_SPMI_SET_POINTS(ht_nldo);
 static DEFINE_SPMI_SET_POINTS(hfs430);
 static DEFINE_SPMI_SET_POINTS(ht_p150);
+static DEFINE_SPMI_SET_POINTS(ht_p600);
 
 static inline int spmi_vreg_read(struct spmi_regulator *vreg, u16 addr, u8 *buf,
 				 int len)
@@ -1464,6 +1470,7 @@ static const struct regulator_ops spmi_hfs430_ops = {
 
 static const struct spmi_regulator_mapping supported_regulators[] = {
 	/*           type subtype dig_min dig_max ltype ops setpoints hpm_min */
+	SPMI_VREG(LDO,   HT_P600,  0, INF, HFS430, hfs430, ht_p600, 10000),
 	SPMI_VREG(LDO,   HT_P150,  0, INF, HFS430, hfs430, ht_p150, 10000),
 	SPMI_VREG(BUCK,  GP_CTL,   0, INF, SMPS,   smps,   smps,   100000),
 	SPMI_VREG(BUCK,  HFS430,   0, INF, HFS430, hfs430, hfs430,  10000),
-- 
2.36.1


  parent reply	other threads:[~2022-07-04 21:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 21:23 [PATCH v6 01/12] dt-bindings: mfd: qcom-spmi-pmic: add support for PMP8074 Robert Marko
2022-07-04 21:23 ` [PATCH v6 02/12] " Robert Marko
2022-07-05 12:37   ` Lee Jones
2022-07-04 21:23 ` [PATCH v6 03/12] dt-bindings: regulator: qcom,spmi-regulator: Convert to dtschema Robert Marko
2022-07-04 21:23 ` [PATCH v6 04/12] regulator: qcom_spmi: add support for HT_P150 Robert Marko
2022-07-04 21:23 ` Robert Marko [this message]
2022-07-04 21:23 ` [PATCH v6 06/12] dt-bindings: regulator: qcom,spmi-regulator: add PMP8074 PMIC Robert Marko
2022-07-04 21:23 ` [PATCH v6 07/12] regulator: qcom_spmi: add support for PMP8074 regulators Robert Marko
2022-07-04 21:23 ` [PATCH v6 08/12] dt-bindings: pinctrl: qcom,pmic-gpio: add PMP8074 Robert Marko
2022-07-06  8:12   ` Krzysztof Kozlowski
2022-07-04 21:23 ` [PATCH v6 09/12] pinctrl: qcom-pmic-gpio: add support for PMP8074 Robert Marko
2022-07-11 11:56   ` Linus Walleij
2022-07-11 20:11     ` Robert Marko
2022-07-04 21:24 ` [PATCH v6 10/12] iio: adc: qcom-spmi-adc5: add ADC5_VREF_VADC to rev2 ADC5 Robert Marko
2022-07-07 17:54   ` Jonathan Cameron
2022-07-04 21:24 ` [PATCH v6 11/12] arm64: dts: qcom: add PMP8074 DTSI Robert Marko
2022-07-06  8:13   ` Krzysztof Kozlowski
2022-07-06 12:27   ` Konrad Dybcio
2022-07-06 15:08     ` Robert Marko
2022-07-04 21:24 ` [PATCH v6 12/12] arm64: dts: qcom: ipq8074-hk01: add VQMMC supply Robert Marko
2022-07-06  8:11 ` [PATCH v6 01/12] dt-bindings: mfd: qcom-spmi-pmic: add support for PMP8074 Krzysztof Kozlowski
2022-07-11 19:10 ` (subset) " 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=20220704212402.1715182-5-robimarko@gmail.com \
    --to=robimarko@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).