From: Andrew Davis <afd@ti.com>
To: "Kory Maincent (TI.com)" <kory.maincent@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>,
Shree Ramamoorthy <s-ramamoorthy@ti.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Bajjuri Praneeth <praneeth@ti.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] mfd: tps65219: Implement LOCK register handling for TPS65214
Date: Wed, 12 Nov 2025 13:03:22 -0600 [thread overview]
Message-ID: <454220b7-81cc-4450-812c-06bfbe527ee2@ti.com> (raw)
In-Reply-To: <20251112-fix_tps65219-v4-1-696a0f55d5d8@bootlin.com>
On 11/12/25 9:14 AM, Kory Maincent (TI.com) wrote:
> The TPS65214 PMIC variant has a LOCK_REG register that prevents writes to
> nearly all registers when locked. Unlock the registers at probe time and
> leave them unlocked permanently.
>
> This approach is justified because:
> - Register locking is very uncommon in typical system operation
> - No code path is expected to lock the registers during runtime
Any other entity in the system that could re-lock these registers?
How about low power modes or other PM handling?
> - Adding a custom regmap write function would add overhead to every
> register write, including voltage changes triggered by CPU OPP
> transitions from the cpufreq governor which could happen quite
> frequently
>
> Cc: stable@vger.kernel.org
> Fixes: 7947219ab1a2d ("mfd: tps65219: Add support for TI TPS65214 PMIC")
> Signed-off-by: Kory Maincent (TI.com) <kory.maincent@bootlin.com>
> ---
> Changes in v4:
> - Move the registers unlock in the probe instead of a custom regmap write
> operation.
>
> Changes in v3:
> - Removed unused variable.
>
> Changes in v2:
> - Setup a custom regmap_bus only for the TPS65214 instead of checking
> the chip_id every time reg_write is called.
> ---
> drivers/mfd/tps65219.c | 7 +++++++
> include/linux/mfd/tps65219.h | 2 ++
> 2 files changed, 9 insertions(+)
>
> diff --git a/drivers/mfd/tps65219.c b/drivers/mfd/tps65219.c
> index 65a952555218d..f1115c5585545 100644
> --- a/drivers/mfd/tps65219.c
> +++ b/drivers/mfd/tps65219.c
> @@ -498,6 +498,13 @@ static int tps65219_probe(struct i2c_client *client)
> return ret;
> }
>
> + if (chip_id == TPS65214) {
> + ret = i2c_smbus_write_byte_data(client, TPS65214_REG_LOCK,
> + TPS65214_LOCK_ACCESS_CMD);
> + if (ret)
> + return ret;
Might be good to print out some error message here, otherwise LGTM,
Reviewed-by: Andrew Davis <afd@ti.com>
> + }
> +
> ret = devm_regmap_add_irq_chip(tps->dev, tps->regmap, client->irq,
> IRQF_ONESHOT, 0, pmic->irq_chip,
> &tps->irq_data);
> diff --git a/include/linux/mfd/tps65219.h b/include/linux/mfd/tps65219.h
> index 55234e771ba73..3abf937191d0c 100644
> --- a/include/linux/mfd/tps65219.h
> +++ b/include/linux/mfd/tps65219.h
> @@ -149,6 +149,8 @@ enum pmic_id {
> #define TPS65215_ENABLE_LDO2_EN_MASK BIT(5)
> #define TPS65214_ENABLE_LDO1_EN_MASK BIT(5)
> #define TPS65219_ENABLE_LDO4_EN_MASK BIT(6)
> +/* Register Unlock */
> +#define TPS65214_LOCK_ACCESS_CMD 0x5a
> /* power ON-OFF sequence slot */
> #define TPS65219_BUCKS_LDOS_SEQUENCE_OFF_SLOT_MASK GENMASK(3, 0)
> #define TPS65219_BUCKS_LDOS_SEQUENCE_ON_SLOT_MASK GENMASK(7, 4)
>
next prev parent reply other threads:[~2025-11-12 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 15:14 [PATCH v4 0/2] Enable 1GHz OPP am335x-bonegreen-eco Kory Maincent (TI.com)
2025-11-12 15:14 ` [PATCH v4 1/2] mfd: tps65219: Implement LOCK register handling for TPS65214 Kory Maincent (TI.com)
2025-11-12 19:03 ` Andrew Davis [this message]
2025-11-13 9:42 ` Kory Maincent
2025-11-12 15:14 ` [PATCH v4 2/2] ARM: dts: am335x-bonegreen-eco: Enable 1GHz OPP by increasing vdd_mpu voltage Kory Maincent (TI.com)
2025-11-27 13:41 ` [PATCH v4 0/2] Enable 1GHz OPP am335x-bonegreen-eco Kory Maincent
2025-12-09 3:09 ` Kevin Hilman
2025-12-09 10:15 ` Kory Maincent
2025-12-12 7:29 ` Lee Jones
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=454220b7-81cc-4450-812c-06bfbe527ee2@ti.com \
--to=afd@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=s-ramamoorthy@ti.com \
--cc=stable@vger.kernel.org \
--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®