Terry Bai

Now the clock driver #278 is ready to be used for dynamically configuring clock rates. As we don't have a complete clock management policy (e.g., which parent clock is better...

> That's good news. Right now all that's needed is to have a known value of clk81 because all the clock divider values are completely arbitrary now based on the...

> Great. I can get onto solving this issue sometime next month unless somebody else gets it first I can replace clk81-related configurations with requests to clock driver now, so...