From: Johan Hovold <johan@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Johan Hovold <johan+linaro@kernel.org>,
Lee Jones <lee@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Mark Brown <broonie@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Das Srinagesh <quic_gurus@quicinc.com>,
Satya Priya <quic_c_skakit@quicinc.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH 12/13] regulator: add pm8008 pmic regulator driver
Date: Thu, 9 May 2024 11:10:41 +0200 [thread overview]
Message-ID: <ZjyTEVLp8VAhQfT5@hovoldconsulting.com> (raw)
In-Reply-To: <CAE-0n52KTZ8G2VuvrDgJ9kAE61YULXY4u6nPP3CYWpg1CBjbXA@mail.gmail.com>
On Wed, May 08, 2024 at 10:37:50PM +0000, Stephen Boyd wrote:
> Quoting Johan Hovold (2024-05-06 08:08:29)
> > +#include <linux/device.h>
> > +#include <linux/kernel.h>
> > +#include <linux/module.h>
> > +#include <linux/of.h>
> > +#include <linux/platform_device.h>
> > +#include <linux/regmap.h>
> > +#include <linux/regulator/driver.h>
> > +
> > +#define VSET_STEP_MV 8
> > +#define VSET_STEP_UV (VSET_STEP_MV * 1000)
> > +
> > +#define LDO_ENABLE_REG(base) ((base) + 0x46)
> > +#define ENABLE_BIT BIT(7)
> > +
> > +#define LDO_VSET_LB_REG(base) ((base) + 0x40)
> > +
> > +#define LDO_STEPPER_CTL_REG(base) ((base) + 0x3b)
> > +#define DEFAULT_VOLTAGE_STEPPER_RATE 38400
> > +#define STEP_RATE_MASK GENMASK(1, 0)
>
> Include bits.h?
Sure.
I wanted to avoid changing Qualcomm's v15 driver too much and
essentially submitted it unchanged except for the probe rework. I'll
take closer look at things like this for v2.
> > +struct pm8008_regulator {
> > + struct regmap *regmap;
> > + struct regulator_desc rdesc;
> > + u16 base;
> > + int step_rate;
>
> Is struct regulator_desc::vsel_step usable for this? If not, can it be
> unsigned?
Not sure, I'll take a look when respinning.
> > +};
> > +static int pm8008_regulator_get_voltage(struct regulator_dev *rdev)
> > +{
> > + struct pm8008_regulator *pm8008_reg = rdev_get_drvdata(rdev);
> > + __le16 mV;
> > + int uV;
>
> Can this be unsigned? Doubt we have negative voltage and this would
> match rdesc.min_uV type.
Makes sense.
> > +
> > + regmap_bulk_read(pm8008_reg->regmap,
> > + LDO_VSET_LB_REG(pm8008_reg->base), (void *)&mV, 2);
>
> Is struct regulator_desc::vsel_reg usable for this?
Will look into that.
> > +
> > + uV = le16_to_cpu(mV) * 1000;
> > + return (uV - pm8008_reg->rdesc.min_uV) / pm8008_reg->rdesc.uV_step;
> > +}
> > +
> > +static inline int pm8008_write_voltage(struct pm8008_regulator *pm8008_reg,
> > + int mV)
> > +{
> > + __le16 vset_raw;
> > +
> > + vset_raw = cpu_to_le16(mV);
> > +
> > + return regmap_bulk_write(pm8008_reg->regmap,
> > + LDO_VSET_LB_REG(pm8008_reg->base),
> > + (const void *)&vset_raw, sizeof(vset_raw));
>
> Is the cast to please sparse?
No idea, I think it's just a stylistic preference that can be dropped.
> > +}
> > +static int pm8008_regulator_set_voltage(struct regulator_dev *rdev,
> > + unsigned int selector)
> > +{
> > + struct pm8008_regulator *pm8008_reg = rdev_get_drvdata(rdev);
> > + int rc, mV;
> > +
> > + rc = regulator_list_voltage_linear_range(rdev, selector);
> > + if (rc < 0)
> > + return rc;
> > +
> > + /* voltage control register is set with voltage in millivolts */
> > + mV = DIV_ROUND_UP(rc, 1000);
> > +
> > + rc = pm8008_write_voltage(pm8008_reg, mV);
> > + if (rc < 0)
> > + return rc;
> > +
> > + return 0;
>
> Can be shorter to save lines
>
> return pm8008_write_voltage(pm8008_reg, mV);
Possibly, but I tend to prefer explicit error paths (e.g. for symmetry).
> > +}
> > +static int pm8008_regulator_probe(struct platform_device *pdev)
> > +{
> > + struct regulator_config reg_config = {};
> > + struct pm8008_regulator *pm8008_reg;
> > + struct device *dev = &pdev->dev;
> > + struct regulator_desc *rdesc;
> > + struct regulator_dev *rdev;
> > + struct regmap *regmap;
> > + unsigned int val;
> > + int rc, i;
> > +
> > + regmap = dev_get_regmap(dev->parent, "secondary");
> > + if (!regmap)
> > + return -EINVAL;
> > +
> > + for (i = 0; i < ARRAY_SIZE(reg_data); i++) {
> > + pm8008_reg = devm_kzalloc(dev, sizeof(*pm8008_reg), GFP_KERNEL);
> > + if (!pm8008_reg)
> > + return -ENOMEM;
> > +
> > + pm8008_reg->regmap = regmap;
> > + pm8008_reg->base = reg_data[i].base;
> > +
> > + /* get slew rate */
> > + rc = regmap_bulk_read(pm8008_reg->regmap,
> > + LDO_STEPPER_CTL_REG(pm8008_reg->base), &val, 1);
> > + if (rc < 0) {
> > + dev_err(dev, "failed to read step rate: %d\n", rc);
>
> Is it step rate or slew rate? The comment doesn't agree with the error
> message.
Noticed that too, can update the comment.
> > + return rc;
> > + }
> > + val &= STEP_RATE_MASK;
> > + pm8008_reg->step_rate = DEFAULT_VOLTAGE_STEPPER_RATE >> val;
> > +
> > + rdesc = &pm8008_reg->rdesc;
> > + rdesc->type = REGULATOR_VOLTAGE;
> > + rdesc->ops = &pm8008_regulator_ops;
> > + rdesc->name = reg_data[i].name;
> > + rdesc->supply_name = reg_data[i].supply_name;
> > + rdesc->of_match = reg_data[i].name;
> > + rdesc->uV_step = VSET_STEP_UV;
> > + rdesc->linear_ranges = reg_data[i].voltage_range;
> > + rdesc->n_linear_ranges = 1;
> > + BUILD_BUG_ON((ARRAY_SIZE(pldo_ranges) != 1) ||
>
> This should be an && not || right?
No, I think this is correct as it stands if the intention is to prevent
anyone from extending either pldo_ranges or nldo_ranges.
> > + (ARRAY_SIZE(nldo_ranges) != 1));
> > +
> > + if (reg_data[i].voltage_range == nldo_ranges) {
> > + rdesc->min_uV = NLDO_MIN_UV;
> > + rdesc->n_voltages = ((NLDO_MAX_UV - NLDO_MIN_UV) / rdesc->uV_step) + 1;
> > + } else {
> > + rdesc->min_uV = PLDO_MIN_UV;
> > + rdesc->n_voltages = ((PLDO_MAX_UV - PLDO_MIN_UV) / rdesc->uV_step) + 1;
> > + }
> > +
> > + rdesc->enable_reg = LDO_ENABLE_REG(pm8008_reg->base);
> > + rdesc->enable_mask = ENABLE_BIT;
> > + rdesc->min_dropout_uV = reg_data[i].min_dropout_uv;
> > + rdesc->regulators_node = of_match_ptr("regulators");
> > +
> > + reg_config.dev = dev->parent;
> > + reg_config.driver_data = pm8008_reg;
> > + reg_config.regmap = pm8008_reg->regmap;
> > +
> > + rdev = devm_regulator_register(dev, rdesc, ®_config);
> > + if (IS_ERR(rdev)) {
> > + rc = PTR_ERR(rdev);
> > + dev_err(dev, "failed to register regulator %s: %d\n",
> > + reg_data[i].name, rc);
> > + return rc;
>
> Could be return dev_err_probe() to simplify.
Possibly, but I think I prefer not using it when there is nothing that
can trigger a probe deferral.
Johan
next prev parent reply other threads:[~2024-05-09 9:10 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 15:08 [PATCH 00/13] arm64: dts: qcom: sc8280xp-x13s: enable pm8008 camera pmic Johan Hovold
2024-05-06 15:08 ` [PATCH 01/13] dt-bindings: mfd: pm8008: add reset gpio Johan Hovold
2024-05-07 6:38 ` Krzysztof Kozlowski
2024-05-08 21:39 ` Stephen Boyd
2024-05-27 13:32 ` Linus Walleij
2024-05-06 15:08 ` [PATCH 02/13] mfd: pm8008: fix regmap irq chip initialisation Johan Hovold
2024-05-06 18:56 ` Andy Shevchenko
2024-05-07 15:01 ` Johan Hovold
2024-05-07 17:16 ` Andy Shevchenko
2024-05-09 8:49 ` Johan Hovold
2024-05-09 13:26 ` Andy Shevchenko
2024-05-06 15:08 ` [PATCH 03/13] mfd: pm8008: deassert reset on probe Johan Hovold
2024-05-06 18:57 ` Andy Shevchenko
2024-05-07 15:15 ` Johan Hovold
2024-05-08 16:12 ` Bryan O'Donoghue
2024-05-09 9:31 ` Johan Hovold
2024-05-29 16:17 ` Johan Hovold
2024-05-29 18:52 ` Bryan O'Donoghue
2024-05-27 13:39 ` Linus Walleij
2024-05-06 15:08 ` [PATCH 04/13] mfd: pm8008: mark regmap structures as const Johan Hovold
2024-05-08 17:37 ` Bryan O'Donoghue
2024-05-08 22:03 ` Stephen Boyd
2024-05-06 15:08 ` [PATCH 05/13] mfd: pm8008: use lower case hex notation Johan Hovold
2024-05-08 17:38 ` Bryan O'Donoghue
2024-05-08 22:03 ` Stephen Boyd
2024-05-06 15:08 ` [PATCH 06/13] mfd: pm8008: rename irq chip Johan Hovold
2024-05-08 17:38 ` Bryan O'Donoghue
2024-05-08 22:04 ` Stephen Boyd
2024-05-06 15:08 ` [PATCH 07/13] mfd: pm8008: drop unused driver data Johan Hovold
2024-05-08 17:40 ` Bryan O'Donoghue
2024-05-08 22:05 ` Stephen Boyd
2024-05-06 15:08 ` [PATCH 08/13] dt-bindings: pinctrl: qcom,pmic-gpio: drop pm8008 Johan Hovold
2024-05-07 6:41 ` Krzysztof Kozlowski
2024-05-08 22:06 ` Stephen Boyd
2024-05-06 15:08 ` [PATCH 09/13] pinctrl: qcom: spmi-gpio: drop broken pm8008 support Johan Hovold
2024-05-08 17:43 ` Bryan O'Donoghue
2024-05-08 22:06 ` Stephen Boyd
2024-05-27 13:35 ` Linus Walleij
2024-05-29 16:12 ` Johan Hovold
2024-05-06 15:08 ` [PATCH 10/13] dt-bindings: mfd: pm8008: rework binding Johan Hovold
2024-05-07 6:43 ` Krzysztof Kozlowski
2024-05-07 15:23 ` Johan Hovold
2024-05-08 22:09 ` Stephen Boyd
2024-05-09 6:57 ` Krzysztof Kozlowski
2024-05-06 15:08 ` [PATCH 11/13] mfd: pm8008: rework driver Johan Hovold
2024-05-06 19:18 ` Andy Shevchenko
2024-05-09 9:42 ` Johan Hovold
2024-05-10 13:15 ` Andy Shevchenko
2024-05-22 6:49 ` Johan Hovold
2024-05-22 7:13 ` Andy Shevchenko
2024-05-22 8:00 ` Johan Hovold
2024-05-08 17:56 ` Bryan O'Donoghue
2024-05-06 15:08 ` [PATCH 12/13] regulator: add pm8008 pmic regulator driver Johan Hovold
2024-05-06 19:09 ` Andy Shevchenko
2024-05-07 15:44 ` Johan Hovold
2024-05-07 17:22 ` Andy Shevchenko
2024-05-07 18:14 ` Krzysztof Kozlowski
2024-05-09 8:57 ` Johan Hovold
2024-05-09 10:48 ` Krzysztof Kozlowski
2024-05-09 12:26 ` Johan Hovold
2024-05-17 9:15 ` Krzysztof Kozlowski
2024-05-08 11:41 ` Mark Brown
2024-05-09 8:53 ` Johan Hovold
2024-05-09 13:24 ` Andy Shevchenko
2024-05-14 13:43 ` Satya Priya Kakitapalli
2024-05-14 22:14 ` Konrad Dybcio
2024-05-29 16:04 ` Johan Hovold
2024-05-14 14:04 ` Satya Priya Kakitapalli
2024-05-14 14:18 ` Andy Shevchenko
2024-05-14 15:04 ` Satya Priya Kakitapalli (Temp)
2024-05-14 16:04 ` Andy Shevchenko
2024-05-07 11:48 ` Konrad Dybcio
2024-05-07 15:52 ` Johan Hovold
2024-05-08 17:55 ` Bryan O'Donoghue
2024-05-08 22:37 ` Stephen Boyd
2024-05-09 9:10 ` Johan Hovold [this message]
2024-05-29 15:55 ` Johan Hovold
2024-05-09 12:07 ` Andy Shevchenko
2024-05-09 12:20 ` Johan Hovold
2024-05-06 15:08 ` [PATCH 13/13] arm64: dts: qcom: sc8280xp-x13s: enable pm8008 camera pmic Johan Hovold
2024-05-08 17:53 ` Bryan O'Donoghue
2024-05-06 20:40 ` [PATCH 00/13] " Rob Herring (Arm)
2024-05-09 8:42 ` Johan Hovold
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=ZjyTEVLp8VAhQfT5@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.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-kernel@vger.kernel.org \
--cc=quic_c_skakit@quicinc.com \
--cc=quic_gurus@quicinc.com \
--cc=robh@kernel.org \
--cc=swboyd@chromium.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