From: Shree Ramamoorthy <s-ramamoorthy@ti.com>
To: Roger Quadros <rogerq@kernel.org>, <lgirdwood@gmail.com>,
<broonie@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <aaro.koskinen@iki.fi>,
<andreas@kemnade.info>, <khilman@baylibre.com>,
<tony@atomide.com>, <jerome.neanne@baylibre.com>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: <m-leonard@ti.com>, <praneeth@ti.com>
Subject: Re: [PATCH v1 7/7] regulator: tps65215: Restructure probe() for multi-PMIC support
Date: Tue, 7 Jan 2025 15:12:27 -0600 [thread overview]
Message-ID: <a76dc55a-5de7-4936-b1f0-af301da0344e@ti.com> (raw)
In-Reply-To: <b3a49df1-372c-46c3-869b-205ddfd18cad@kernel.org>
Hi,
On 1/4/25 12:47 PM, Roger Quadros wrote:
>
> On 26/12/2024 23:54, Shree Ramamoorthy wrote:
>> The probe() function will now utilize the register_regulators() and
>> request_irqs() helper functions defined in the previous patch. Probe() will
>> cycle through common (overlapping) regulators and irqs first, and then
>> handle device-specific resources identified using the chip_data struct.
>>
>> Signed-off-by: Shree Ramamoorthy <s-ramamoorthy@ti.com>
>> ---
>> drivers/regulator/tps65219-regulator.c | 66 +++++++++++---------------
>> 1 file changed, 27 insertions(+), 39 deletions(-)
>>
>> diff --git a/drivers/regulator/tps65219-regulator.c b/drivers/regulator/tps65219-regulator.c
>> index 8469ee89802c..b27888fd1fa8 100644
>> --- a/drivers/regulator/tps65219-regulator.c
>> +++ b/drivers/regulator/tps65219-regulator.c
>> @@ -413,54 +413,42 @@ static int tps65219_request_irqs(struct tps65219_regulator_irq_type *irq_types,
>> static int tps65219_regulator_probe(struct platform_device *pdev)
>> {
>> struct tps65219 *tps = dev_get_drvdata(pdev->dev.parent);
>> - struct regulator_dev *rdev;
>> struct regulator_config config = { };
>> - int i;
>> int error;
>> - int irq;
>> struct tps65219_regulator_irq_data *irq_data;
>> - struct tps65219_regulator_irq_type *irq_type;
>> + struct chip_data *pmic;
> reverse xmas tree.
>
>>
>> - config.dev = tps->dev;
>> - config.driver_data = tps;
>> - config.regmap = tps->regmap;
>>
>> - for (i = 0; i < ARRAY_SIZE(regulators); i++) {
>> - rdev = devm_regulator_register(&pdev->dev, ®ulators[i],
>> - &config);
>> - if (IS_ERR(rdev))
>> - return dev_err_probe(tps->dev, PTR_ERR(rdev),
>> - "Failed to register %s regulator\n",
>> - regulators[i].name);
>> - }
>> -
>> - irq_data = devm_kmalloc(tps->dev,
>> - ARRAY_SIZE(tps65219_regulator_irq_types) *
>> - sizeof(struct tps65219_regulator_irq_data),
>> - GFP_KERNEL);
>> - if (!irq_data)
>> - return -ENOMEM;
>> -
>> - for (i = 0; i < ARRAY_SIZE(tps65219_regulator_irq_types); ++i) {
>> - irq_type = &tps65219_regulator_irq_types[i];
>> + enum pmic_id chip = platform_get_device_id(pdev)->driver_data;
>>
>> - irq = platform_get_irq_byname(pdev, irq_type->irq_name);
>> - if (irq < 0)
>> - return -EINVAL;
> need a new line after declarations.
>
>> + pmic = &chip_info_table[chip];
>>
>> - irq_data[i].dev = tps->dev;
>> - irq_data[i].type = irq_type;
>> + config.dev = tps->dev;
>> + config.driver_data = tps;
>> + config.regmap = tps->regmap;
>>
>> - error = devm_request_threaded_irq(tps->dev, irq, NULL,
>> - tps65219_regulator_irq_handler,
>> - IRQF_ONESHOT,
>> - irq_type->irq_name,
>> - &irq_data[i]);
>> - if (error) {
>> - dev_err(tps->dev, "failed to request %s IRQ %d: %d\n",
>> - irq_type->irq_name, irq, error);
>> + error = tps65219_register_regulators(pmic->common_rdesc, tps,
>> + &pdev->dev, config, pmic->common_rdesc_size);
>> + if (error)
> maybe you could use goto and do any cleanup
> and in the end use dev_err_probe().
Looking through all of the feedback/ideas, I am planning to have the helper functions return the error,
use goto to check and return dev_err_probe if an error is detected. This should hopefully minimize the
amount of repeated error checks in this probe function. Thank you for the feedback!
>> + return error;
>> +
>> + error = tps65219_register_regulators(pmic->rdesc, tps, &pdev->dev,
>> + config, pmic->rdesc_size);
>> + if (error)
>> + return error;
>> +
>> + irq_data = devm_kmalloc(tps->dev, pmic->common_irq_size, GFP_KERNEL);
>> + error = tps65219_request_irqs(pmic->common_irq_types, tps, pdev,
>> + irq_data, pmic->common_irq_size);
>> + if (error)
>> + return error;
>> +
>> + if (chip == TPS65219) {
>> + irq_data = devm_kmalloc(tps->dev, pmic->dev_irq_size, GFP_KERNEL);
>> + error = tps65219_request_irqs(pmic->irq_types, tps, pdev,
>> + irq_data, pmic->dev_irq_size);
>> + if (error)
>> return error;
>> - }
>> }
>>
>> return 0;
--
Best,
Shree Ramamoorthy
PMIC Software Engineer
prev parent reply other threads:[~2025-01-07 21:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 21:54 [PATCH v1 0/7] Add TI TPS65215 PMIC Regulator Support Shree Ramamoorthy
2024-12-26 21:54 ` [PATCH v1 1/7] regulator: dt-bindings: Add TI TPS65215 PMIC bindings Shree Ramamoorthy
2024-12-27 17:45 ` Conor Dooley
2025-01-04 18:28 ` Roger Quadros
2024-12-26 21:54 ` [PATCH v1 2/7] regulator: tps65215: Update platform_device_id table Shree Ramamoorthy
2025-01-01 10:49 ` Christophe JAILLET
2024-12-26 21:54 ` [PATCH v1 3/7] regulator: tps65215: Update function & struct names Shree Ramamoorthy
2025-01-04 18:35 ` Roger Quadros
2024-12-26 21:54 ` [PATCH v1 4/7] regulator: tps65215: Update IRQ structs to include TPS65215 Shree Ramamoorthy
2024-12-26 21:54 ` [PATCH v1 5/7] regulator: tps65215: Add chip_data struct for multi-PMIC support Shree Ramamoorthy
2024-12-26 21:54 ` [PATCH v1 6/7] regulator: tps65215: Define probe() helper functions Shree Ramamoorthy
2025-01-01 11:01 ` Christophe JAILLET
2025-01-02 23:41 ` Shree Ramamoorthy
2025-01-03 13:10 ` Christophe JAILLET
2025-01-04 18:42 ` Roger Quadros
2025-01-04 18:45 ` Roger Quadros
2025-01-06 22:02 ` Shree Ramamoorthy
2025-01-06 22:57 ` Andrew Davis
2025-01-07 21:09 ` Shree Ramamoorthy
2024-12-26 21:54 ` [PATCH v1 7/7] regulator: tps65215: Restructure probe() for multi-PMIC support Shree Ramamoorthy
2025-01-01 11:04 ` Christophe JAILLET
2025-01-02 23:46 ` Shree Ramamoorthy
2025-01-04 18:47 ` Roger Quadros
2025-01-07 21:12 ` Shree Ramamoorthy [this message]
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=a76dc55a-5de7-4936-b1f0-af301da0344e@ti.com \
--to=s-ramamoorthy@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jerome.neanne@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m-leonard@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.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