From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, agross@kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Jorge Ramirez <jorge.ramirez-ortiz@linaro.org>
Subject: Re: [PATCH v4 7/7] regulator: qcom_spmi: add PMS405 SPMI regulator
Date: Thu, 13 Jun 2019 14:37:11 -0700 [thread overview]
Message-ID: <20190613213711.GD4814@minitux> (raw)
In-Reply-To: <20190613212707.5966-2-jeffrey.l.hugo@gmail.com>
On Thu 13 Jun 14:27 PDT 2019, Jeffrey Hugo wrote:
> From: Jorge Ramirez <jorge.ramirez-ortiz@linaro.org>
>
> The PMS405 has 5 HFSMPS and 13 LDO regulators,
>
> This commit adds support for one of the 5 HFSMPS regulators (s3) to
> the spmi regulator driver.
>
> The PMIC HFSMPS 430 regulators have 8 mV step size and a voltage
> control scheme consisting of two 8-bit registers defining a 16-bit
> voltage set point in units of millivolts
>
> S3 controls the cpu voltages (s3 is a buck regulator of type HFS430);
> it is therefore required so we can enable voltage scaling for safely
> running cpufreq.
>
> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
> Signed-off-by: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> ---
> drivers/regulator/qcom_spmi-regulator.c | 43 +++++++++++++++++++++++--
> 1 file changed, 40 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/regulator/qcom_spmi-regulator.c b/drivers/regulator/qcom_spmi-regulator.c
> index c8791b036c53..debe4dc74d27 100644
> --- a/drivers/regulator/qcom_spmi-regulator.c
> +++ b/drivers/regulator/qcom_spmi-regulator.c
> @@ -105,6 +105,7 @@ enum spmi_regulator_logical_type {
> SPMI_REGULATOR_LOGICAL_TYPE_ULT_HO_SMPS,
> SPMI_REGULATOR_LOGICAL_TYPE_ULT_LDO,
> SPMI_REGULATOR_LOGICAL_TYPE_FTSMPS426,
> + SPMI_REGULATOR_LOGICAL_TYPE_HFS430,
> };
>
> enum spmi_regulator_type {
> @@ -157,6 +158,7 @@ enum spmi_regulator_subtype {
> SPMI_REGULATOR_SUBTYPE_ULT_HF_CTL2 = 0x0e,
> SPMI_REGULATOR_SUBTYPE_ULT_HF_CTL3 = 0x0f,
> SPMI_REGULATOR_SUBTYPE_ULT_HF_CTL4 = 0x10,
> + SPMI_REGULATOR_SUBTYPE_HFS430 = 0x0a,
> };
>
> enum spmi_common_regulator_registers {
> @@ -302,6 +304,8 @@ enum spmi_common_control_register_index {
> /* Clock rate in kHz of the FTSMPS426 regulator reference clock. */
> #define SPMI_FTSMPS426_CLOCK_RATE 4800
>
> +#define SPMI_HFS430_CLOCK_RATE 1600
> +
> /* Minimum voltage stepper delay for each step. */
> #define SPMI_FTSMPS426_STEP_DELAY 2
>
> @@ -515,6 +519,10 @@ static struct spmi_voltage_range ult_pldo_ranges[] = {
> SPMI_VOLTAGE_RANGE(0, 1750000, 1750000, 3337500, 3337500, 12500),
> };
>
> +static struct spmi_voltage_range hfs430_ranges[] = {
> + SPMI_VOLTAGE_RANGE(0, 320000, 320000, 2040000, 2040000, 8000),
> +};
> +
> static DEFINE_SPMI_SET_POINTS(pldo);
> static DEFINE_SPMI_SET_POINTS(nldo1);
> static DEFINE_SPMI_SET_POINTS(nldo2);
> @@ -530,6 +538,7 @@ static DEFINE_SPMI_SET_POINTS(ult_lo_smps);
> static DEFINE_SPMI_SET_POINTS(ult_ho_smps);
> static DEFINE_SPMI_SET_POINTS(ult_nldo);
> static DEFINE_SPMI_SET_POINTS(ult_pldo);
> +static DEFINE_SPMI_SET_POINTS(hfs430);
>
> static inline int spmi_vreg_read(struct spmi_regulator *vreg, u16 addr, u8 *buf,
> int len)
> @@ -1399,12 +1408,26 @@ static struct regulator_ops spmi_ftsmps426_ops = {
> .set_pull_down = spmi_regulator_common_set_pull_down,
> };
>
> +static struct regulator_ops spmi_hfs430_ops = {
> + .enable = regulator_enable_regmap,
> + .disable = regulator_disable_regmap,
> + .is_enabled = regulator_is_enabled_regmap,
> + .set_voltage_sel = spmi_regulator_ftsmps426_set_voltage,
> + .set_voltage_time_sel = spmi_regulator_set_voltage_time_sel,
> + .get_voltage = spmi_regulator_ftsmps426_get_voltage,
> + .map_voltage = spmi_regulator_single_map_voltage,
> + .list_voltage = spmi_regulator_common_list_voltage,
> + .set_mode = spmi_regulator_ftsmps426_set_mode,
> + .get_mode = spmi_regulator_ftsmps426_get_mode,
> +};
> +
> /* Maximum possible digital major revision value */
> #define INF 0xFF
>
> static const struct spmi_regulator_mapping supported_regulators[] = {
> /* type subtype dig_min dig_max ltype ops setpoints hpm_min */
> SPMI_VREG(BUCK, GP_CTL, 0, INF, SMPS, smps, smps, 100000),
> + SPMI_VREG(BUCK, HFS430, 0, INF, HFS430, hfs430, hfs430, 10000),
> SPMI_VREG(LDO, N300, 0, INF, LDO, ldo, nldo1, 10000),
> SPMI_VREG(LDO, N600, 0, 0, LDO, ldo, nldo2, 10000),
> SPMI_VREG(LDO, N1200, 0, 0, LDO, ldo, nldo2, 10000),
> @@ -1572,7 +1595,8 @@ static int spmi_regulator_init_slew_rate(struct spmi_regulator *vreg)
> return ret;
> }
>
> -static int spmi_regulator_init_slew_rate_ftsmps426(struct spmi_regulator *vreg)
> +static int spmi_regulator_init_slew_rate_ftsmps426(struct spmi_regulator *vreg,
> + int clock_rate)
> {
> int ret;
> u8 reg = 0;
> @@ -1589,7 +1613,7 @@ static int spmi_regulator_init_slew_rate_ftsmps426(struct spmi_regulator *vreg)
> delay >>= SPMI_FTSMPS426_STEP_CTRL_DELAY_SHIFT;
>
> /* slew_rate has units of uV/us */
> - slew_rate = SPMI_FTSMPS426_CLOCK_RATE * range->step_uV;
> + slew_rate = clock_rate * range->step_uV;
> slew_rate /= 1000 * (SPMI_FTSMPS426_STEP_DELAY << delay);
> slew_rate *= SPMI_FTSMPS426_STEP_MARGIN_NUM;
> slew_rate /= SPMI_FTSMPS426_STEP_MARGIN_DEN;
> @@ -1741,7 +1765,14 @@ static int spmi_regulator_of_parse(struct device_node *node,
> return ret;
> break;
> case SPMI_REGULATOR_LOGICAL_TYPE_FTSMPS426:
> - ret = spmi_regulator_init_slew_rate_ftsmps426(vreg);
> + ret = spmi_regulator_init_slew_rate_ftsmps426(vreg,
> + SPMI_FTSMPS426_CLOCK_RATE);
> + if (ret)
> + return ret;
> + break;
> + case SPMI_REGULATOR_LOGICAL_TYPE_HFS430:
> + ret = spmi_regulator_init_slew_rate_ftsmps426(vreg,
> + SPMI_HFS430_CLOCK_RATE);
> if (ret)
> return ret;
> break;
> @@ -1909,6 +1940,11 @@ static const struct spmi_regulator_data pm8005_regulators[] = {
> { }
> };
>
> +static const struct spmi_regulator_data pms405_regulators[] = {
> + { "s3", 0x1a00, "vdd_s3"},
> + { }
> +};
> +
> static const struct of_device_id qcom_spmi_regulator_match[] = {
> { .compatible = "qcom,pm8005-regulators", .data = &pm8005_regulators },
> { .compatible = "qcom,pm8841-regulators", .data = &pm8841_regulators },
> @@ -1916,6 +1952,7 @@ static const struct of_device_id qcom_spmi_regulator_match[] = {
> { .compatible = "qcom,pm8941-regulators", .data = &pm8941_regulators },
> { .compatible = "qcom,pm8994-regulators", .data = &pm8994_regulators },
> { .compatible = "qcom,pmi8994-regulators", .data = &pmi8994_regulators },
> + { .compatible = "qcom,pms405-regulators", .data = &pms405_regulators },
> { }
> };
> MODULE_DEVICE_TABLE(of, qcom_spmi_regulator_match);
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-06-13 21:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 21:24 [PATCH v4 0/7] PM8005 and PMS405 regulator support Jeffrey Hugo
2019-06-13 21:25 ` [PATCH v4 1/7] regulator: qcom_spmi: enable linear range info Jeffrey Hugo
2019-06-13 21:25 ` [PATCH v4 2/7] regulator: qcom_spmi: Refactor get_mode/set_mode Jeffrey Hugo
2019-06-13 21:32 ` Bjorn Andersson
2019-06-17 15:24 ` Applied "regulator: qcom_spmi: Refactor get_mode/set_mode" to the regulator tree Mark Brown
2019-06-17 15:24 ` Applied "regulator: qcom_spmi: enable linear range info" " Mark Brown
2019-06-13 21:25 ` [PATCH v4 3/7] dt-bindings: qcom_spmi: Document PM8005 regulators Jeffrey Hugo
2019-06-13 21:25 ` [PATCH v4 4/7] regulator: qcom_spmi: Add support for PM8005 Jeffrey Hugo
2019-06-17 15:05 ` Mark Brown
2019-06-17 15:17 ` Jeffrey Hugo
2019-06-17 16:03 ` Mark Brown
2019-06-17 17:07 ` Jeffrey Hugo
2019-06-17 18:37 ` Mark Brown
[not found] ` <CAOCk7NpbZwAreGpVCvF2yFBDJKbAxBZ23oncfF_SyEwoiC2+PQ@mail.gmail.com>
[not found] ` <20190617192413.GI5316@sirena.org.uk>
2019-06-17 19:41 ` Jeffrey Hugo
2019-06-13 21:26 ` [PATCH v4 5/7] arm64: dts: msm8998-mtp: Add pm8005_s1 regulator Jeffrey Hugo
2019-06-13 21:27 ` [PATCH v4 6/7] dt-bindings: qcom_spmi: Document pms405 support Jeffrey Hugo
2019-06-13 21:27 ` [PATCH v4 7/7] regulator: qcom_spmi: add PMS405 SPMI regulator Jeffrey Hugo
2019-06-13 21:37 ` Bjorn Andersson [this message]
2019-06-13 21:37 ` [PATCH v4 6/7] dt-bindings: qcom_spmi: Document pms405 support Bjorn Andersson
2019-06-17 14:58 ` [PATCH v4 0/7] PM8005 and PMS405 regulator support Mark Brown
2019-06-17 15:04 ` Jeffrey Hugo
2019-06-17 15:12 ` 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=20190613213711.GD4814@minitux \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jeffrey.l.hugo@gmail.com \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).