[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c744cf7a70a3f97722146215a7620cfb.sboyd@kernel.org>
Date: Thu, 05 Sep 2024 11:09:52 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: alexandre.belloni@...tlin.com, claudiu beznea <claudiu.beznea@...on.dev>, conor+dt@...nel.org, geert+renesas@...der.be, krzk+dt@...nel.org, magnus.damm@...il.com, mturquette@...libre.com, p.zabel@...gutronix.de, robh@...nel.org
Cc: linux-renesas-soc@...r.kernel.org, linux-clk@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-rtc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
Subject: Re: [PATCH v3 07/12] arm64: dts: renesas: r9a08g045: Add VBATTB node
Quoting claudiu beznea (2024-09-04 05:17:30)
> On 03.09.2024 22:48, Stephen Boyd wrote:
> >
> > The node name should be something like clock-<frequency> but if the
> > frequency is different per-board then I don't know what should happen
> > here.
>
> The frequency should be always around 32768 Hz but not necessarily exactly
> 32768 Hz. It depends on what is installed on the board, indeed. RTC can do
> time error adjustments based on the variations around 32768 Hz.
>
> > Can you leave the vbattb_xtal phandle up above and then require
> > the node to be defined in the board with the proper frequency after the
> > dash?
>
> Is it OK for you something like this (applied on top of this series)?
Yes, it's too bad we can't append to a property in DT, or somehow leave
alone certain cells and only modify one of them.
Powered by blists - more mailing lists