mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kory Maincent <kory.maincent@bootlin.com>
To: Andrew Davis <afd@ti.com>
Cc: <linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Bajjuri Praneeth <praneeth@ti.com>,
	Ramamoorthy Shree <s-ramamoorthy@ti.com>,
	<thomas.petazzoni@bootlin.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Andreas Kemnade <andreas@kemnade.info>,
	Kevin Hilman <khilman@baylibre.com>,
	Roger Quadros <rogerq@kernel.org>,
	Tony Lindgren <tony@atomide.com>, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH] mfd: tps65219: Implement LOCK register handling for TPS65214
Date: Thu, 6 Nov 2025 10:34:43 +0100	[thread overview]
Message-ID: <20251106103443.607c8276@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <cadef564-3ef2-435a-9611-ac007f32c10d@ti.com>

On Wed, 5 Nov 2025 14:52:21 -0600
Andrew Davis <afd@ti.com> wrote:

> On 11/5/25 11:47 AM, Kory Maincent wrote:
> > From: "Kory Maincent (TI.com)" <kory.maincent@bootlin.com>
> > 
> > The TPS65214 PMIC variant has a LOCK_REG register that prevents writes to
> > nearly all registers.
> > 
> > Implement custom regmap operations that automatically unlock before writes
> > and re-lock afterwards for TPS65214, while leaving other chip variants
> > unaffected.
> > 
> > The implementation follows the regmap-i2c design pattern.
> > 
> > Signed-off-by: Kory Maincent (TI.com) <kory.maincent@bootlin.com>
> > ---
> >   drivers/mfd/tps65219.c       | 53 +++++++++++++++++++++++++++++++++++-
> >   include/linux/mfd/tps65219.h |  3 ++
> >   2 files changed, 55 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/mfd/tps65219.c b/drivers/mfd/tps65219.c
> > index 65a952555218d..1d8a06afb1048 100644
> > --- a/drivers/mfd/tps65219.c
> > +++ b/drivers/mfd/tps65219.c
> > @@ -473,6 +473,55 @@ static const struct tps65219_chip_data
> > chip_info_table[] = { },
> >   };
> >   
> > +static int tps65219_reg_write(void *context, unsigned int reg, unsigned
> > int val) +{
> > +	struct i2c_client *i2c = context;
> > +	struct tps65219 *tps;
> > +	int ret;
> > +
> > +	if (val > 0xff || reg > 0xff)
> > +		return -EINVAL;
> > +
> > +	tps = i2c_get_clientdata(i2c);
> > +	if (tps->chip_id == TPS65214) {
> > +		ret = i2c_smbus_write_byte_data(i2c, TPS65214_REG_LOCK,
> > +						TPS65214_LOCK_ACCESS_CMD);
> > +		if (ret)
> > +			return ret;
> > +	}
> > +
> > +	ret = i2c_smbus_write_byte_data(i2c, reg, val);
> > +	if (ret)
> > +		return ret;
> > +
> > +	if (tps->chip_id == TPS65214)
> > +		return i2c_smbus_write_byte_data(i2c, TPS65214_REG_LOCK,
> > 0); +
> > +	return 0;
> > +}
> > +
> > +static int tps65219_reg_read(void *context, unsigned int reg, unsigned int
> > *val) +{
> > +	struct i2c_client *i2c = context;
> > +	int ret;
> > +
> > +	if (reg > 0xff)
> > +		return -EINVAL;
> > +
> > +	ret = i2c_smbus_read_byte_data(i2c, reg);
> > +	if (ret < 0)
> > +		return ret;
> > +
> > +	*val = ret;
> > +
> > +	return 0;
> > +}
> > +
> > +static const struct regmap_bus tps65219_regmap_bus = {
> > +	.reg_write = tps65219_reg_write,
> > +	.reg_read = tps65219_reg_read,
> > +};
> > +
> >   static int tps65219_probe(struct i2c_client *client)
> >   {
> >   	struct tps65219 *tps;
> > @@ -490,8 +539,10 @@ static int tps65219_probe(struct i2c_client *client)
> >   	tps->dev = &client->dev;
> >   	chip_id = (uintptr_t)i2c_get_match_data(client);
> >   	pmic = &chip_info_table[chip_id];
> > +	tps->chip_id = chip_id;
> >   
> > -	tps->regmap = devm_regmap_init_i2c(client,
> > &tps65219_regmap_config);
> > +	tps->regmap = devm_regmap_init(&client->dev, &tps65219_regmap_bus,
> > client,
> > +				       &tps65219_regmap_config);  
> 
> Why not do the (tps->chip_id == TPS65214) check here and only setup the
> special regmap_bus for the TPS65214. Then you don't need to do the checks
> every time reg_write is called.

Yes indeed that's a better idea!

Thanks,
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

      reply	other threads:[~2025-11-06  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 17:47 Kory Maincent
2025-11-05 20:52 ` Andrew Davis
2025-11-06  9:34   ` Kory Maincent [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=20251106103443.607c8276@kmaincent-XPS-13-7390 \
    --to=kory.maincent@bootlin.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=afd@ti.com \
    --cc=andreas@kemnade.info \
    --cc=khilman@baylibre.com \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=praneeth@ti.com \
    --cc=rogerq@kernel.org \
    --cc=s-ramamoorthy@ti.com \
    --cc=thomas.petazzoni@bootlin.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

all inboxes | Powered by JetHome®