From: Shree Ramamoorthy <s-ramamoorthy@ti.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
<aaro.koskinen@iki.fi>, <andreas@kemnade.info>,
<khilman@baylibre.com>, <rogerq@kernel.org>, <tony@atomide.com>,
<lee@kernel.org>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <m-leonard@ti.com>, <praneeth@ti.com>
Subject: Re: [PATCH v2 1/2] mfd: tps65215: Add support for TI TPS65215 PMIC
Date: Mon, 6 Jan 2025 16:13:07 -0600 [thread overview]
Message-ID: <1e23f5d3-4af1-47d3-a977-ab25dde7e1ec@ti.com> (raw)
In-Reply-To: <58e4118c-f705-4565-842e-2baca4ea5abd@wanadoo.fr>
Hi,
On 1/4/2025 5:30 AM, Christophe JAILLET wrote:
> Le 03/01/2025 à 23:57, Shree Ramamoorthy a écrit :
>> Use chip ID and chip_data struct to differentiate between devices in
>> probe(). Add TPS65215 resource information. Update descriptions and
>> copyright information to reflect the driver supports 2 PMIC devices.
>>
>> Signed-off-by: Shree Ramamoorthy <s-ramamoorthy@ti.com>
>
> ...
>
>> @@ -218,10 +333,29 @@ static const struct regmap_irq_chip
>> tps65219_irq_chip = {
>> .sub_reg_offsets = tps65219_sub_irq_offsets,
>> };
>> +struct tps65219_chip_data {
>
> Maybe tps6521x_chip_data?
> (and if so, same for gpio-tps65219.c)
>
I tried to keep tps65219 as the main prefix where possible to avoid the confusion
that the function applies to all devices starting with TPS6521X, when this
driver doesn't. I will revert any functions that start with tps6521x to avoid that
confusion as well.
>> + const struct regmap_irq_chip *irq_chip;
>> + const struct mfd_cell *cells;
>> + int n_cells;
>> +};
>> +
>> +static struct tps65219_chip_data chip_info_table[] = {
>> + [TPS65215] = {
>> + .irq_chip = &tps65215_irq_chip,
>> + .cells = tps65215_cells,
>> + .n_cells = ARRAY_SIZE(tps65215_cells),
>> + },
>> + [TPS65219] = {
>> + .irq_chip = &tps65219_irq_chip,
>> + .cells = tps65219_cells,
>> + .n_cells = ARRAY_SIZE(tps65219_cells),
>> + },
>> +};
>
> ...
>
>> @@ -291,7 +427,10 @@ static int tps65219_probe(struct i2c_client
>> *client)
>> }
>> static const struct of_device_id of_tps65219_match_table[] = {
>> - { .compatible = "ti,tps65219", },
>> + { .compatible = "ti,tps65215", .data = (void *)TPS65215, },
>> + { .compatible = "ti,tps65219", .data = (void *)TPS65219, },
>> + { .compatible = "ti,tps65219", .data = (void *)TPS65219, },
>> + { .compatible = "ti,tps65215", .data = (void *)TPS65215, },
>> {}
>
> Entries look duplicated.
>
Thanks for catching this. I have applied this feedback!
>> };
>
> ...
>
> CJ
>
next prev parent reply other threads:[~2025-01-06 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 22:57 [PATCH v2 0/2] Add TI TPS65215 PMIC MFD Support Shree Ramamoorthy
2025-01-03 22:57 ` [PATCH v2 1/2] mfd: tps65215: Add support for TI TPS65215 PMIC Shree Ramamoorthy
2025-01-04 11:30 ` Christophe JAILLET
2025-01-06 22:13 ` Shree Ramamoorthy [this message]
2025-01-04 18:10 ` Roger Quadros
2025-01-06 22:20 ` Shree Ramamoorthy
2025-01-03 22:57 ` [PATCH v2 2/2] mfd: tps65215: Remove regmap_read check Shree Ramamoorthy
2025-01-04 18:16 ` Roger Quadros
2025-01-06 22:18 ` Shree Ramamoorthy
2025-01-07 12:47 ` Roger Quadros
2025-01-07 18:45 ` Shree Ramamoorthy
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=1e23f5d3-4af1-47d3-a977-ab25dde7e1ec@ti.com \
--to=s-ramamoorthy@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=christophe.jaillet@wanadoo.fr \
--cc=khilman@baylibre.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m-leonard@ti.com \
--cc=praneeth@ti.com \
--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