linux-kernel - Re: [PATCH 5/6] arm64: dts: renesas: r9a09g057: Add RTC node

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: <d6956eba2f99faedf7e6e28cb23d95a36101e6a9.camel@pengutronix.de>
Date: Mon, 20 Oct 2025 10:32:05 +0200
From: Philipp Zabel <p.zabel@...gutronix.de>
To: Ovidiu Panait <ovidiu.panait.rb@...esas.com>, Biju Das	
 <biju.das.jz@...renesas.com>, Claudiu Beznea
 <claudiu.beznea.uj@...renesas.com>,  "alexandre.belloni@...tlin.com"	
 <alexandre.belloni@...tlin.com>, "robh@...nel.org" <robh@...nel.org>, 
 "krzk+dt@...nel.org"	 <krzk+dt@...nel.org>, "conor+dt@...nel.org"
 <conor+dt@...nel.org>,  "geert+renesas@...der.be"	
 <geert+renesas@...der.be>, "magnus.damm" <magnus.damm@...il.com>, 
 "mturquette@...libre.com"	 <mturquette@...libre.com>, "sboyd@...nel.org"
 <sboyd@...nel.org>
Cc: "linux-rtc@...r.kernel.org" <linux-rtc@...r.kernel.org>, 
 "linux-renesas-soc@...r.kernel.org"
	 <linux-renesas-soc@...r.kernel.org>, "devicetree@...r.kernel.org"
	 <devicetree@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	 <linux-kernel@...r.kernel.org>, "linux-clk@...r.kernel.org"
	 <linux-clk@...r.kernel.org>
Subject: Re: [PATCH 5/6] arm64: dts: renesas: r9a09g057: Add RTC node

On Mo, 2025-10-20 at 08:13 +0000, Ovidiu Panait wrote:
> Hi Biju,
> 
> > -----Original Message-----
> > From: Biju Das <biju.das.jz@...renesas.com>
> > Sent: Sunday, October 19, 2025 1:16 PM
> > To: Ovidiu Panait <ovidiu.panait.rb@...esas.com>; Claudiu Beznea
> > <claudiu.beznea.uj@...renesas.com>; alexandre.belloni@...tlin.com;
> > robh@...nel.org; krzk+dt@...nel.org; conor+dt@...nel.org;
> > geert+renesas@...der.be; magnus.damm <magnus.damm@...il.com>;
> > mturquette@...libre.com; sboyd@...nel.org; p.zabel@...gutronix.de
> > Cc: linux-rtc@...r.kernel.org; linux-renesas-soc@...r.kernel.org;
> > devicetree@...r.kernel.org; linux-kernel@...r.kernel.org; linux-
> > clk@...r.kernel.org
> > Subject: RE: [PATCH 5/6] arm64: dts: renesas: r9a09g057: Add RTC node
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Ovidiu Panait <ovidiu.panait.rb@...esas.com>
> > > Sent: 19 October 2025 10:21
> > > Subject: [PATCH 5/6] arm64: dts: renesas: r9a09g057: Add RTC node
> > > 
> > > Add RTC node to Renesas RZ/V2H ("R9A09G057") SoC DTSI.
> > > 
> > > Signed-off-by: Ovidiu Panait <ovidiu.panait.rb@...esas.com>
> > > ---
> > >  arch/arm64/boot/dts/renesas/r9a09g057.dtsi | 14 ++++++++++++++
> > >  1 file changed, 14 insertions(+)
> > > 
> > > diff --git a/arch/arm64/boot/dts/renesas/r9a09g057.dtsi
> > b/arch/arm64/boot/dts/renesas/r9a09g057.dtsi
> > > index 40b15f1db930..e426b9978e22 100644
> > > --- a/arch/arm64/boot/dts/renesas/r9a09g057.dtsi
> > > +++ b/arch/arm64/boot/dts/renesas/r9a09g057.dtsi
> > > @@ -591,6 +591,20 @@ wdt3: watchdog@...00400 {
> > >  			status = "disabled";
> > >  		};
> > > 
> > > +		rtc: rtc@...00800 {
> > > +			compatible = "renesas,r9a09g057-rtca3", "renesas,rz-
> > rtca3";
> > > +			reg = <0 0x11c00800 0 0x400>;
> > > +			interrupts = <GIC_SPI 524 IRQ_TYPE_EDGE_RISING>,
> > > +				     <GIC_SPI 525 IRQ_TYPE_EDGE_RISING>,
> > > +				     <GIC_SPI 526 IRQ_TYPE_EDGE_RISING>;
> > > +			interrupt-names = "alarm", "period", "carry";
> > > +			clocks = <&cpg CPG_MOD 0x53>, <&rtxin_clk>;
> > > +			clock-names = "bus", "counter";
> > > +			power-domains = <&cpg>;
> > > +			resets = <&cpg 0x79>, <&cpg 0x7a>;
> > 
> > Missing reset-names??
> > 
> 
> The resets are retrieved using devm_reset_control_array_get_shared(),

The device tree bindings should be designed independently from the
driver implementation.

> which does not rely on named reset entries. This keeps the
> implementation minimal and keeps it in sync with RZ/G3S, which also
> does not take the RTC reset by its name.
> 
> For this reason, I kept the rtca3 bindings without a reset-names property.

There is no need to use the reset names in the driver if they are just
toggled all at once, but unless you can guarantee that there will never
be a need to tell them apart, it would be safer to give them a name.

regards
Philipp