> Hence I think it should be handled in the driver. I knew it ;) If we change the MSTP driver, we should do it in a generic way. MSTP clocks which should/should not change the parent's clock rate can be anywhere. My best bet so far would be encoding this in DT, because all the heuristics I could think of seem too fragile to me. That's because I assume in a clock tree, anything is possible. Changing DTs having MSTP clocks is quite intrusive, though...
Attachment:
signature.asc
Description: PGP signature
