linux-kernel - Re: [PATCH 1/3] arm64: dts: rockchip: Enable OTP controller for RK3562

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4721118.KgjxqYA5nG@diego>
Date: Mon, 09 Feb 2026 21:23:09 +0100
From: Heiko Stübner <heiko@...ech.de>
To: Jonas Karlman <jonas@...boo.se>
Cc:
 "linux-arm-kernel@...ts.infradead.org"
 <linux-arm-kernel@...ts.infradead.org>,
 "linux-rockchip@...ts.infradead.org" <linux-rockchip@...ts.infradead.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "kever.yang@...k-chips.com" <kever.yang@...k-chips.com>,
 "finley.xiao@...k-chips.com" <finley.xiao@...k-chips.com>,
 "w@....eu" <w@....eu>
Subject:
 Re: [PATCH 1/3] arm64: dts: rockchip: Enable OTP controller for RK3562

Am Montag, 9. Februar 2026, 17:54:51 Mitteleuropäische Normalzeit schrieb Jonas Karlman:
> Hi Heiko,
> 
> Thanks for including my RK3528 patches :-)
> 
> On 2/5/2026 10:23 PM, Heiko Stuebner wrote:
> > Enable the One Time Programmable Controller (OTPC) in RK3562 and add
> > an initial nvmem fixed layout.
> > 
> > Signed-off-by: Heiko Stuebner <heiko@...ech.de>
> > ---
> >  arch/arm64/boot/dts/rockchip/rk3562.dtsi | 46 ++++++++++++++++++++++++
> >  1 file changed, 46 insertions(+)
> > 
> > diff --git a/arch/arm64/boot/dts/rockchip/rk3562.dtsi b/arch/arm64/boot/dts/rockchip/rk3562.dtsi
> > index f84676b47b27..07626dba21bf 100644
> > --- a/arch/arm64/boot/dts/rockchip/rk3562.dtsi
> > +++ b/arch/arm64/boot/dts/rockchip/rk3562.dtsi
> > @@ -1093,6 +1093,52 @@ sdmmc1: mmc@...90000 {
> >  			status = "disabled";
> >  		};
> >  
> > +		otp: otp@...30000 {
> 
> I noticed that the node names is not consistent for all three patches in
> this series.
> 
> A quick grep at Linux src also suggest that efuse@ being the most common
> node name used for similar otpc/efuse, efuse is also listed under
> 2.2.2 Generic Names Recommendation in DT spec.
> 
> Maybe the nodes should be renamed to use efuse@ or something else?

Fine by me :-)
So we'll make this efuse@ for all 3 newly added otp controllers.

Heiko