[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176795712434.1656708.9000200659822594124.b4-ty@kernel.org>
Date: Fri, 09 Jan 2026 11:12:04 +0000
From: Lee Jones <lee@...nel.org>
To: Aaro Koskinen <aaro.koskinen@....fi>,
Andreas Kemnade <andreas@...nade.info>, Kevin Hilman <khilman@...libre.com>,
Roger Quadros <rogerq@...nel.org>, Tony Lindgren <tony@...mide.com>,
Lee Jones <lee@...nel.org>, Shree Ramamoorthy <s-ramamoorthy@...com>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
"Kory Maincent (TI.com)" <kory.maincent@...tlin.com>
Cc: Andrew Davis <afd@...com>, Bajjuri Praneeth <praneeth@...com>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: (subset) [PATCH v5 1/2] mfd: tps65219: Implement LOCK register
handling for TPS65214
On Thu, 18 Dec 2025 16:06:28 +0100, 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
> - 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
>
> [...]
Applied, thanks!
[1/2] mfd: tps65219: Implement LOCK register handling for TPS65214
commit: 9ef5418bc106177f2330f7bf383f8a2cf29aa435
--
Lee Jones [李琼斯]
Powered by blists - more mailing lists