From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shree Ramamoorthy <s-ramamoorthy@ti.com>,
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, christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH v1 1/1] mfd: tps65214: Add support for TI TPS65214 PMIC
Date: Fri, 17 Jan 2025 10:22:08 +0100 [thread overview]
Message-ID: <33852928-c4df-4966-8fab-b6638fef2486@kernel.org> (raw)
In-Reply-To: <20250116223915.430263-2-s-ramamoorthy@ti.com>
On 16/01/2025 23:39, Shree Ramamoorthy wrote:
> Use chip ID and chip_data struct to differentiate between 3 PMIC devices in
> probe(). Add TPS65214 resource information. Update descriptions and
> copyright information to reflect the driver supports 3 PMIC devices.
>
> Signed-off-by: Shree Ramamoorthy <s-ramamoorthy@ti.com>
> ---
> static struct tps65219_chip_data chip_info_table[] = {
> + [TPS65214] = {
> + .irq_chip = &tps65214_irq_chip,
> + .cells = tps65214_cells,
> + .n_cells = ARRAY_SIZE(tps65214_cells),
> + },
> [TPS65215] = {
> .irq_chip = &tps65215_irq_chip,
> .cells = tps65215_cells,
> @@ -421,6 +542,7 @@ static int tps65219_probe(struct i2c_client *client)
> }
>
> static const struct of_device_id of_tps65219_match_table[] = {
> + { .compatible = "ti,tps65214", .data = (void *)TPS65214, },
Where is the binding patch? It cannot be sent separately.
> { .compatible = "ti,tps65215", .data = (void *)TPS65215, },
> { .compatible = "ti,tps65219", .data = (void *)TPS65219, },
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-17 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 22:39 [PATCH v1 0/1] Add TI TPS65214 PMIC MFD Support Shree Ramamoorthy
2025-01-16 22:39 ` [PATCH v1 1/1] mfd: tps65214: Add support for TI TPS65214 PMIC Shree Ramamoorthy
2025-01-17 9:22 ` Krzysztof Kozlowski [this message]
2025-01-17 9:23 ` [PATCH v1 0/1] Add TI TPS65214 PMIC MFD Support Krzysztof Kozlowski
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=33852928-c4df-4966-8fab-b6638fef2486@kernel.org \
--to=krzk@kernel.org \
--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=s-ramamoorthy@ti.com \
--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