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 v2 12/14] regulator: tps6594-regulator: Add TI TPS65224 PMIC regulators
Date: Thu, 29 Feb 2024 15:42:50 +0100 [thread overview]
Message-ID: <CZHN4S2QW6MY.KKKHHRPPY4ZG@baylibre.com> (raw)
In-Reply-To: <20240223093701.66034-13-bhargav.r@ltts.com>
On Fri Feb 23, 2024 at 10:36 AM CET, Bhargav Raviprakash wrote:
> From: Nirmala Devi Mal Nadar <m.nirmaladevi@ltts.com>
> @@ -122,6 +131,27 @@ static const struct linear_range ldos_4_ranges[] = {
> REGULATOR_LINEAR_RANGE(1200000, 0x20, 0x74, 25000),
> };
>
> +/* Voltage range for TPS65224 Bucks and LDOs */
> +static const struct linear_range tps65224_bucks_1_ranges[] = {
You prefixed your arrays with `tps65224` and that makes sense. However
you should also prefix the old ones with `tps6594` then.
This applies to the whole driver.
> @@ -374,11 +518,17 @@ static int tps6594_request_reg_irqs(struct platform_device *pdev,
> {
> struct tps6594_regulator_irq_type *irq_type;
> struct tps6594 *tps = dev_get_drvdata(pdev->dev.parent);
> - int j;
> + size_t j;
> int irq;
> int error;
> + size_t interrupt_cnt;
>
> - for (j = 0; j < REGS_INT_NB; j++) {
> + /* Number of interrupts supported by each voltage source */
> + interrupt_cnt = (tps->chip_id == TPS6594) ?
> + ARRAY_SIZE(tps6594_buck1_irq_types) :
> + ARRAY_SIZE(tps65224_buck1_irq_types);
The comment is not adding anything, the name is clear and ARRAY_SIZE is
quite explicit.
> + for (i = 0; i < LDO_NB; i++) {
> + if (ldo_configured[i] == 1)
> + continue;
>
> - error = tps6594_request_reg_irqs(pdev, rdev, irq_data,
> - tps6594_ldos_irq_types[i],
> - &irq_idx);
> - if (error)
> - return error;
> + 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;
> +
> + rdev = devm_regulator_register(&pdev->dev, &ldo_regs[i], &config);
> + if (IS_ERR(rdev))
> + return dev_err_probe(tps->dev, PTR_ERR(rdev),
> + "failed to register %s regulator\n", pdev->name);
> +
> + error = tps6594_request_reg_irqs(pdev, rdev, irq_data, ldos_irq_types[i], &irq_idx);
> + if (error)
> + return error;
There is an indentation missing on the content of the `for` loop.
Best regards,
--
Esteban "Skallwar" Blanc
BayLibre
next prev parent reply other threads:[~2024-02-29 14:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 9:36 [PATCH v2 00/14] Add support for TI TPS65224 PMIC Bhargav Raviprakash
2024-02-23 9:36 ` [PATCH v2 01/14] mfd: tps6594: Add register definitions " Bhargav Raviprakash
2024-02-26 11:07 ` Julien Panis
2024-02-23 9:36 ` [PATCH v2 02/14] mfd: tps6594: use volatile_table instead of volatile_reg Bhargav Raviprakash
2024-02-26 11:15 ` Julien Panis
2024-02-23 9:36 ` [PATCH v2 03/14] mfd: tps6594: add regmap config in match data Bhargav Raviprakash
2024-02-26 11:35 ` Julien Panis
2024-02-23 9:36 ` [PATCH v2 04/14] dt-bindings: mfd: ti,tps6594: Add TI TPS65224 PMIC Bhargav Raviprakash
2024-02-23 18:37 ` Conor Dooley
2024-02-23 9:36 ` [PATCH v2 05/14] mfd: tps6594-i2c: Add TI TPS65224 PMIC I2C Bhargav Raviprakash
2024-02-26 11:40 ` Julien Panis
2024-02-23 9:36 ` [PATCH v2 06/14] mfd: tps6594-spi: Add TI TPS65224 PMIC SPI Bhargav Raviprakash
2024-02-26 11:52 ` Julien Panis
2024-02-23 9:36 ` [PATCH v2 07/14] mfd: tps6594-core: Add TI TPS65224 PMIC core Bhargav Raviprakash
2024-02-26 12:17 ` Julien Panis
2024-02-23 9:36 ` [PATCH v2 08/14] misc: tps6594-pfsm: Add TI TPS65224 PMIC PFSM Bhargav Raviprakash
2024-02-26 12:43 ` Julien Panis
2024-03-07 9:13 ` Bhargav Raviprakash
2024-02-23 9:36 ` [PATCH v2 09/14] misc: tps6594-esm: reversion check limited to TPS6594 family Bhargav Raviprakash
2024-02-26 12:56 ` Julien Panis
2024-02-23 9:36 ` [PATCH v2 10/14] misc: tps6594-esm: use regmap_field Bhargav Raviprakash
2024-02-23 9:36 ` [PATCH v2 11/14] misc: tps6594-esm: Add TI TPS65224 PMIC ESM Bhargav Raviprakash
2024-02-23 9:36 ` [PATCH v2 12/14] regulator: tps6594-regulator: Add TI TPS65224 PMIC regulators Bhargav Raviprakash
2024-02-29 13:58 ` Mark Brown
2024-03-07 9:15 ` Bhargav Raviprakash
2024-02-29 14:42 ` Esteban Blanc [this message]
2024-02-29 14:49 ` Mark Brown
2024-03-07 9:18 ` Bhargav Raviprakash
2024-03-07 9:17 ` Bhargav Raviprakash
2024-02-23 9:37 ` [PATCH v2 13/14] pinctrl: pinctrl-tps6594: Add TPS65224 PMIC pinctrl and GPIO Bhargav Raviprakash
2024-02-29 13:24 ` Linus Walleij
2024-03-07 9:19 ` Bhargav Raviprakash
2024-03-07 9:36 ` Julien Panis
2024-02-29 13:56 ` Esteban Blanc
2024-02-23 9:37 ` [PATCH v2 14/14] arch: arm64: dts: ti: k3-am62p5-sk: Add TPS65224 PMIC support in AM62P dts Bhargav Raviprakash
2024-02-29 17:49 ` [PATCH v2 00/14] Add support for TI TPS65224 PMIC Lee Jones
2024-03-07 9:47 ` 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=CZHN4S2QW6MY.KKKHHRPPY4ZG@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®