<Danct12>
krzk: in your talk, i assume you mean that the syscon should be the clock and reset provider all in one node, there shouldn't be any child, right?
<krzk>
Danct12: I don't remember exactly the case, but most likely yes
__lore__ has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
_lore_ has joined #linux-msm
<Danct12>
what if you want two separate driver to access one compatible? it doesn't seem to be practical to make it a separate thing because the reset value is next to the enable/disable reg for each clock
<krzk>
I don't understamnd but it feels like you are mixing driver model with DT. They are completely independent.
<Danct12>
yeah, this is now a driver model question.. from what i've seen, only one driver gets to claim it, once claimed the other driver wouldn't probe
<krzk>
yeah, node gets populated. You can depoppulate it and there are few cases of it.