Quoting Tony Lindgren (2020-02-21 09:10:30) > Currently enabling clkctrl clock on am4 can fail for RTC as the clock > parent is wrong for RTC. > > Fixes: 76a1049b84dd ("clk: ti: am43xx: add new clkctrl data for am43xx") > Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx> > --- > > It is unclear if we can end up with RTC hung with the current mainline > kernel in some cases. Probing RTC with device tree data only seems to > trigger this every time. It's small enough and if it's annoying enough we can probably put it into clk-fixes to get it fixed for this release instead of waiting. Can Tero ack it?