Thread (4 messages) 4 messages, 3 authors, 2015-02-02

Clock Regression in next-20150130 caused by cb75a8fcd14e

From: tony@atomide.com (Tony Lindgren)
Date: 2015-02-02 16:22:06
Also in: linux-omap, lkml

* Mike Turquette [off-list ref] [150201 15:29]:
Quoting Tony Lindgren (2015-01-30 17:04:44)
quoted
Hi all,

Looks like commit cb75a8fcd14e ("clk: Add rate constraints to clocks")
causes a regression on at least omaps where the serial console either
does not show anything, or just prints garbage.

Reverting cb75a8fcd14e makes things work again on next-20150130.

Any ideas?
Stephen posted a patch[0] to fix this. I've squashed that into Tomeu's
commit that you reference above and my Panda board is booting fine once
again.

[0] http://lkml.kernel.org/r/[ref]

Please let me know if any other issues pop up. There are new WARNs for
OMAP3+ boards introduced by a different patch from Tomeu, but this is
really because the OMAP DPLL and FAPLL code are dereferencing struct clk
pointers when they should not be and is a separate issue from the
constraints patch (with a separate email thread).
Seems Linux next is broken again. Now we omaps get tons of:

clock: dpll_abe_ck failed transition to 'locked'
WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:925 clk_disable+0x28/0x34()

and 

WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/dpll3xxx.c:436
omap3_noncore_dpll_enable+0xdc/0x10c()

Regards,

Tony
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help