Stephen Boyd <sboyd@xxxxxxxxxxxxxx> writes:
On 08/03/2015 12:58 PM, Robert Jarzmik wrote:Ah yes, good point, v2 on its way.
Clocks 0 to 31 are on CKENA, and not CKENB. The clock register namesDid you want a fixes tag to send this back to stable?
were inadequately inverted. As a consequence, all clock operations were
happening on CKENB, because almost all but 2 clocks are on CKENA.
As the clocks were activated by the bootloader in the former tests, it
escaped the testing that the wrong clock gate was manipulated. The error
was revealed by changing the pxa3xx-and driver to a module, where tupon
unloading the wrong clock was disabled in CKENB.
Signed-off-by: Robert Jarzmik <robert.jarzmik@xxxxxxx>
---
Stephen and Mike, do you think this can still get in -rc6 ?