From: Roger Quadros <rogerq@kernel.org>
To: Shree Ramamoorthy <s-ramamoorthy@ti.com>,
aaro.koskinen@iki.fi, andreas@kemnade.info, khilman@baylibre.com,
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 v3 1/2] mfd: tps65215: Remove regmap_read check
Date: Mon, 20 Jan 2025 14:25:53 +0200 [thread overview]
Message-ID: <37028baa-d0d2-4cb0-938b-0653eeb118bf@kernel.org> (raw)
In-Reply-To: <20250113230750.124843-2-s-ramamoorthy@ti.com>
On 14/01/2025 01:07, Shree Ramamoorthy wrote:
> The chipid macro/variable and regmap_read function call is not needed
> because the TPS65219_REG_TI_DEV_ID register value is not a consistent value
> across TPS65219 PMIC config versions. Reading from the DEV_ID register
> without a consistent value to compare it to isn't useful. There isn't a
> way to verify the match data ID is the same ID read from the DEV_ID device
> register. 0xF0 isn't a DEV_ID value consistent across TPS65219 NVM
> configurations.
>
> For TPS65215, there is a consistent value in bits 5-0 of the DEV_ID
> register. However, there are other error checks in place within probe()
> that apply to both PMICs rather than keeping this isolated check for one
> PMIC.
>
> Signed-off-by: Shree Ramamoorthy <s-ramamoorthy@ti.com>
subject should be "mfd: tps65219:.."?
> ---
> drivers/mfd/tps65219.c | 6 ------
> include/linux/mfd/tps65219.h | 7 +++++--
> 2 files changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/mfd/tps65219.c b/drivers/mfd/tps65219.c
> index 081c5a30b04a..15b874ee59e5 100644
> --- a/drivers/mfd/tps65219.c
> +++ b/drivers/mfd/tps65219.c
> @@ -246,12 +246,6 @@ static int tps65219_probe(struct i2c_client *client)
> if (ret)
> return ret;
>
> - ret = regmap_read(tps->regmap, TPS65219_REG_TI_DEV_ID, &chipid);
> - if (ret) {
> - dev_err(tps->dev, "Failed to read device ID: %d\n", ret);
> - return ret;
> - }
> -
But now chipid has no users. So please drop that variable as well.
> ret = devm_mfd_add_devices(tps->dev, PLATFORM_DEVID_AUTO,
> tps65219_cells, ARRAY_SIZE(tps65219_cells),
> NULL, 0, regmap_irq_get_domain(tps->irq_data));
> diff --git a/include/linux/mfd/tps65219.h b/include/linux/mfd/tps65219.h
> index 546bceec7173..0d88e92ff8f2 100644
> --- a/include/linux/mfd/tps65219.h
> +++ b/include/linux/mfd/tps65219.h
> @@ -13,8 +13,11 @@
> #include <linux/regmap.h>
> #include <linux/regulator/driver.h>
>
> -/* TPS chip id list */
> -#define TPS65219 0xF0
> +/* Chip id list*/
> +enum pmic_id {
> + TPS65215,
> + TPS65219,
> +};
This change is not part of subject. Please merge it with next patch.
>
> /* I2C ID for TPS65219 part */
> #define TPS65219_I2C_ID 0x24
--
cheers,
-roger
next prev parent reply other threads:[~2025-01-20 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 23:07 [PATCH v3 0/2] Add TI TPS65215 PMIC MFD Support Shree Ramamoorthy
2025-01-13 23:07 ` [PATCH v3 1/2] mfd: tps65215: Remove regmap_read check Shree Ramamoorthy
2025-01-20 12:25 ` Roger Quadros [this message]
2025-01-21 20:22 ` Shree Ramamoorthy
2025-01-13 23:07 ` [PATCH v3 2/2] mfd: tps65215: Add support for TI TPS65215 PMIC 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=37028baa-d0d2-4cb0-938b-0653eeb118bf@kernel.org \
--to=rogerq@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=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
Powered by JetHome