13:41 <robher> bamse: sm8450-samsung-r0q.dts is broken in your tree. You might not have noticed because it looks like it got dropped from the makefile and doesn't build unless you give it explicitly (which my dtb checks does).

13:48 <bamse> robher: weird, not sure how that happened... thanks for letting me know!

14:32 <krzk> bamse: that patch should not have been merged (if it was)

14:33 <krzk> It carries wrong SoB and I retracted my Ack after noticing it https://lore.kernel.org/all/1da99d0e-3ccc-473b-8f1f-0d00d206e746@kernel.org/

14:33 <krzk> But I also do not see any emails from you that you applied it

14:35 <krzk> ah, you applied earlier version from Eric https://lore.kernel.org/all/20250615204438.1130213-2-ghatto404@gmail.com/

14:41 <bamse> krzk: yeah, i didn't notice that there was later versions, with discussion - and my dtb checker didn't catch any issues; as it wasn't added to the makefile...

14:41 <bamse> krzk: pushing out a revert

16:23 <CounterPillow> When a clock needs a certain other clock to be enabled just to have the registers for clock control accessible, is that a parent of said clock or is it a clock of the clock controller(?) of which this clock is a part of?

16:24 <CounterPillow> e.g., I cannot read the status of the clock if said other clock is not enabled, and that's pretty much the first thing the dependant clock's prepare function does.

16:57 <mmind00> CounterPillow: for getting even register access, I'd say that is a clock supplying the 2nd clock-controller

16:58 <mmind00> like the power-line supplying the transformer station to "do" something", but not the power getting transformed

16:59 <CounterPillow> Okay, hmmm. The clock driver this is interfacing with currently has absolutely no provisions for even having a clock in the DT, so this will be fun