From: "Esteban Blanc" <eblanc@baylibre.com>
To: "Bhargav Raviprakash" <bhargav.r@ltts.com>,
<linux-kernel@vger.kernel.org>
Cc: <m.nirmaladevi@ltts.com>, <lee@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<jpanis@baylibre.com>, <devicetree@vger.kernel.org>,
<arnd@arndb.de>, <gregkh@linuxfoundation.org>,
<lgirdwood@gmail.com>, <broonie@kernel.org>,
<linus.walleij@linaro.org>, <linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <nm@ti.com>,
<vigneshr@ti.com>, <kristo@kernel.org>
Subject: Re: [PATCH v3 09/11] regulator: tps6594-regulator: Add TI TPS65224 PMIC regulators
Date: Thu, 14 Mar 2024 12:28:00 +0100 [thread overview]
Message-ID: <CZTFR87IG7MI.11DN441APOPE3@baylibre.com> (raw)
In-Reply-To: <20240308103455.242705-10-bhargav.r@ltts.com>
On Fri Mar 8, 2024 at 11:34 AM CET, Bhargav Raviprakash wrote:
> From: Nirmala Devi Mal Nadar <m.nirmaladevi@ltts.com>
>
> Add support for TPS65224 regulators (bucks and LDOs) to TPS6594 driver as
> they have significant functional overlap. TPS65224 PMIC has 4 buck
> regulators and 3 LDOs. BUCK12 can operate in dual phase.
> The output voltages are configurable and are meant to supply power to the
> main processor and other components.
>
> Signed-off-by: Nirmala Devi Mal Nadar <m.nirmaladevi@ltts.com>
> Signed-off-by: Bhargav Raviprakash <bhargav.r@ltts.com>
> ---
> drivers/regulator/Kconfig | 4 +-
> drivers/regulator/tps6594-regulator.c | 236 +++++++++++++++++++++++---
> 2 files changed, 215 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/regulator/tps6594-regulator.c b/drivers/regulator/tps6594-regulator.c
> index b7f0c8779..37d76c483 100644
> --- a/drivers/regulator/tps6594-regulator.c
> +++ b/drivers/regulator/tps6594-regulator.c
> @@ -412,14 +562,20 @@ static int tps6594_regulator_probe(struct platform_device *pdev)
> struct tps6594_ext_regulator_irq_data *irq_ext_reg_data;
> struct tps6594_regulator_irq_type *irq_type;
> u8 buck_configured[BUCK_NB] = { 0 };
> + u8 ldo_configured[LDO_NB] = { 0 };
> u8 buck_multi[MULTI_PHASE_NB] = { 0 };
> static const char * const multiphases[] = {"buck12", "buck123", "buck1234", "buck34"};
`multiphases` should prefixed like the new one.
> + static const char * const tps65224_multiphases[] = {"buck12"};
> @@ -495,25 +660,30 @@ static int tps6594_regulator_probe(struct platform_device *pdev)
> if (!irq_data)
> return -ENOMEM;
>
> - for (i = 0; i < MULTI_PHASE_NB; i++) {
> + for (i = 0; i < multi_phase_cnt; i++) {
> if (buck_multi[i] == 0)
> continue;
>
> + const struct regulator_desc *multi_regs = (tps->chip_id == TPS65224) ?
> + tps65224_multi_regs :
> + tps6594_multi_regs;
This should be declared at the top of the function.
> rdev = devm_regulator_register(&pdev->dev, &multi_regs[i], &config);
> - if (IS_ERR(rdev))
> - return dev_err_probe(tps->dev, PTR_ERR(rdev),
> - "failed to register %s regulator\n",
> - pdev->name);
> + if (IS_ERR(rdev))
> + return dev_err_probe(tps->dev, PTR_ERR(rdev),
> + "failed to register %s regulator\n",
> + pdev->name);
The indentation of the `if` looks odd. You should revert this.
> @@ -537,21 +707,34 @@ static int tps6594_regulator_probe(struct platform_device *pdev)
> if (buck_configured[i] == 1)
> continue;
>
> - rdev = devm_regulator_register(&pdev->dev, &buck_regs[i], &config);
> + const struct regulator_desc *buck_cfg = (tps->chip_id == TPS65224) ?
> + tps65224_buck_regs : buck_regs;
Same here, should be at the top of the function.
> - /* LP8764 dosen't have LDO */
> + /* LP8764 doesn't have LDO */
> if (tps->chip_id != LP8764) {
> - for (i = 0; i < ARRAY_SIZE(ldo_regs); i++) {
> + for (i = 0; i < LDO_NB; i++) {
> + if (ldo_configured[i] == 1)
> + continue;
> +
> + struct tps6594_regulator_irq_type **ldos_irq_types =
> + (tps->chip_id == TPS65224) ?
> + tps65224_ldos_irq_types : tps6594_ldos_irq_types;
> +
> + const struct regulator_desc *ldo_regs =
> + (tps->chip_id == TPS65224) ?
> + tps65224_ldo_regs : tps6594_ldo_regs;
Should be at the top of the function, please fix this in the whole file.
Best regards,
--
Esteban "Skallwar" Blanc
BayLibre
WARNING: multiple messages have this Message-ID (diff)
From: "Esteban Blanc" <eblanc@baylibre.com>
To: "Bhargav Raviprakash" <bhargav.r@ltts.com>,
<linux-kernel@vger.kernel.org>
Cc: <m.nirmaladevi@ltts.com>, <lee@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<jpanis@baylibre.com>, <devicetree@vger.kernel.org>,
<arnd@arndb.de>, <gregkh@linuxfoundation.org>,
<lgirdwood@gmail.com>, <broonie@kernel.org>,
<linus.walleij@linaro.org>, <linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <nm@ti.com>,
<vigneshr@ti.com>, <kristo@kernel.org>
Subject: Re: [PATCH v3 09/11] regulator: tps6594-regulator: Add TI TPS65224 PMIC regulators
Date: Thu, 14 Mar 2024 12:28:00 +0100 [thread overview]
Message-ID: <CZTFR87IG7MI.11DN441APOPE3@baylibre.com> (raw)
In-Reply-To: <20240308103455.242705-10-bhargav.r@ltts.com>
On Fri Mar 8, 2024 at 11:34 AM CET, Bhargav Raviprakash wrote:
> From: Nirmala Devi Mal Nadar <m.nirmaladevi@ltts.com>
>
> Add support for TPS65224 regulators (bucks and LDOs) to TPS6594 driver as
> they have significant functional overlap. TPS65224 PMIC has 4 buck
> regulators and 3 LDOs. BUCK12 can operate in dual phase.
> The output voltages are configurable and are meant to supply power to the
> main processor and other components.
>
> Signed-off-by: Nirmala Devi Mal Nadar <m.nirmaladevi@ltts.com>
> Signed-off-by: Bhargav Raviprakash <bhargav.r@ltts.com>
> ---
> drivers/regulator/Kconfig | 4 +-
> drivers/regulator/tps6594-regulator.c | 236 +++++++++++++++++++++++---
> 2 files changed, 215 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/regulator/tps6594-regulator.c b/drivers/regulator/tps6594-regulator.c
> index b7f0c8779..37d76c483 100644
> --- a/drivers/regulator/tps6594-regulator.c
> +++ b/drivers/regulator/tps6594-regulator.c
> @@ -412,14 +562,20 @@ static int tps6594_regulator_probe(struct platform_device *pdev)
> struct tps6594_ext_regulator_irq_data *irq_ext_reg_data;
> struct tps6594_regulator_irq_type *irq_type;
> u8 buck_configured[BUCK_NB] = { 0 };
> + u8 ldo_configured[LDO_NB] = { 0 };
> u8 buck_multi[MULTI_PHASE_NB] = { 0 };
> static const char * const multiphases[] = {"buck12", "buck123", "buck1234", "buck34"};
`multiphases` should prefixed like the new one.
> + static const char * const tps65224_multiphases[] = {"buck12"};
> @@ -495,25 +660,30 @@ static int tps6594_regulator_probe(struct platform_device *pdev)
> if (!irq_data)
> return -ENOMEM;
>
> - for (i = 0; i < MULTI_PHASE_NB; i++) {
> + for (i = 0; i < multi_phase_cnt; i++) {
> if (buck_multi[i] == 0)
> continue;
>
> + const struct regulator_desc *multi_regs = (tps->chip_id == TPS65224) ?
> + tps65224_multi_regs :
> + tps6594_multi_regs;
This should be declared at the top of the function.
> rdev = devm_regulator_register(&pdev->dev, &multi_regs[i], &config);
> - if (IS_ERR(rdev))
> - return dev_err_probe(tps->dev, PTR_ERR(rdev),
> - "failed to register %s regulator\n",
> - pdev->name);
> + if (IS_ERR(rdev))
> + return dev_err_probe(tps->dev, PTR_ERR(rdev),
> + "failed to register %s regulator\n",
> + pdev->name);
The indentation of the `if` looks odd. You should revert this.
> @@ -537,21 +707,34 @@ static int tps6594_regulator_probe(struct platform_device *pdev)
> if (buck_configured[i] == 1)
> continue;
>
> - rdev = devm_regulator_register(&pdev->dev, &buck_regs[i], &config);
> + const struct regulator_desc *buck_cfg = (tps->chip_id == TPS65224) ?
> + tps65224_buck_regs : buck_regs;
Same here, should be at the top of the function.
> - /* LP8764 dosen't have LDO */
> + /* LP8764 doesn't have LDO */
> if (tps->chip_id != LP8764) {
> - for (i = 0; i < ARRAY_SIZE(ldo_regs); i++) {
> + for (i = 0; i < LDO_NB; i++) {
> + if (ldo_configured[i] == 1)
> + continue;
> +
> + struct tps6594_regulator_irq_type **ldos_irq_types =
> + (tps->chip_id == TPS65224) ?
> + tps65224_ldos_irq_types : tps6594_ldos_irq_types;
> +
> + const struct regulator_desc *ldo_regs =
> + (tps->chip_id == TPS65224) ?
> + tps65224_ldo_regs : tps6594_ldo_regs;
Should be at the top of the function, please fix this in the whole file.
Best regards,
--
Esteban "Skallwar" Blanc
BayLibre
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-14 11:28 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 10:34 [PATCH v3 00/11] Add support for TI TPS65224 PMIC Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
2024-03-08 10:34 ` [PATCH v3 01/11] mfd: tps6594: Add register definitions " Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
2024-03-08 11:24 ` Julien Panis
2024-03-08 11:24 ` Julien Panis
2024-03-20 10:13 ` Bhargav Raviprakash
2024-03-20 10:13 ` Bhargav Raviprakash
2024-03-08 10:34 ` [PATCH v3 02/11] mfd: tps6594: use volatile_table instead of volatile_reg Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
2024-03-08 10:34 ` [PATCH v3 03/11] mfd: tps6594: add regmap config in match data Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
2024-03-14 13:30 ` Dan Carpenter
2024-03-14 13:30 ` Dan Carpenter
2024-03-20 10:22 ` Bhargav Raviprakash
2024-03-20 10:22 ` Bhargav Raviprakash
2024-03-08 10:34 ` [PATCH v3 04/11] dt-bindings: mfd: ti,tps6594: Add TI TPS65224 PMIC Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
2024-03-08 10:34 ` [PATCH v3 05/11] mfd: tps6594-i2c: Add TI TPS65224 PMIC I2C Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
2024-03-08 10:34 ` [PATCH v3 06/11] mfd: tps6594-spi: Add TI TPS65224 PMIC SPI Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
2024-03-08 10:34 ` [PATCH v3 07/11] mfd: tps6594-core: Add TI TPS65224 PMIC core Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
2024-03-08 10:34 ` [PATCH v3 08/11] misc: tps6594-pfsm: Add TI TPS65224 PMIC PFSM Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
2024-03-08 10:58 ` Julien Panis
2024-03-08 10:58 ` Julien Panis
2024-03-08 10:34 ` [PATCH v3 09/11] regulator: tps6594-regulator: Add TI TPS65224 PMIC regulators Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
2024-03-14 11:28 ` Esteban Blanc [this message]
2024-03-14 11:28 ` Esteban Blanc
2024-03-20 10:15 ` Bhargav Raviprakash
2024-03-20 10:15 ` Bhargav Raviprakash
2024-03-14 13:30 ` Dan Carpenter
2024-03-14 13:30 ` Dan Carpenter
2024-03-20 10:17 ` Bhargav Raviprakash
2024-03-20 10:17 ` Bhargav Raviprakash
2024-03-08 10:34 ` [PATCH v3 10/11] pinctrl: pinctrl-tps6594: Add TPS65224 PMIC pinctrl and GPIO Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
2024-03-14 11:29 ` Esteban Blanc
2024-03-14 11:29 ` Esteban Blanc
2024-03-20 10:18 ` Bhargav Raviprakash
2024-03-20 10:18 ` Bhargav Raviprakash
2024-03-08 10:34 ` [PATCH v3 11/11] arch: arm64: dts: ti: k3-am62p5-sk: Add TPS65224 PMIC support in AM62P dts Bhargav Raviprakash
2024-03-08 10:34 ` Bhargav Raviprakash
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=CZTFR87IG7MI.11DN441APOPE3@baylibre.com \
--to=eblanc@baylibre.com \
--cc=arnd@arndb.de \
--cc=bhargav.r@ltts.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jpanis@baylibre.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.nirmaladevi@ltts.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.