Quoting Geert Uytterhoeven (2024-09-06 00:28:38) > Hi Stephen, > > On Thu, Sep 5, 2024 at 8:09 PM Stephen Boyd <sboyd@xxxxxxxxxx> wrote: > > 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. > > My main objections are that (1) this approach is different than the one used > for all other external clock inputs on Renesas SoCs, and (2) this requires > duplicating part of the clocks property in all board DTS files. > Can 'clock-ranges' be used here? Leave the cell as null in the SoC dtsi file and then fill it in with clocks property at the parent node. I think you'd have to use clock-names for this though.
