Quoting Eric Anholt (2018-03-13 09:56:57)

Stephen Boyd sboyd@kernel.org writes:

...

What exactly is going on here? It sounds like the framework isn't aware of the 'on/off' boot state of certain clks (a known problem) and that's causing some sort of problem when changing rates? This usually happens with PLLs that are enabled at boot time and can't support their rate changing when they're enabled. We really should start reading on/off state and "hand off" that enabled state to something in the framework so we at least know if a clk is enabled or not out of boot. There was some work on clk handoff done a while ago by Mike that never landed which may be useful to finish this off. Maybe we can pass that enabled state off to the clk we always create for a clk_hw structure at registration time and then have clk_disable_unused operate on that clk pointer at late init.

Yes, the usual problem of clk not handling boot-time clock state well.

That said, it's patch 1 that's critical for fixing many of our users, and we need that in as soon as possible. #2 is also reviewed and ready.

Got it. I'll pick up the first two then.