From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Thu, 18 Dec 2014 08:41:23 -0800 Subject: OMAP 4430 SDP: rather sick with recent kernels In-Reply-To: <20141217172333.GE23854@atomide.com> References: <20141217095252.GH11502@n2100.arm.linux.org.uk> <20141217172333.GE23854@atomide.com> Message-ID: <20141218164122.GH23854@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Tony Lindgren [141217 09:28]: > > And then there are these too in the current mainline that are > clock related: > > omap4xxx_dt_clk_init: failed to configure ABE DPLL! > ... > clock: dpll_abe_ck failed transition to 'locked' > clock: dpll_abe_ck failed transition to 'locked' > clock: dpll_abe_ck failed transition to 'locked' > ------------[ cut here ]------------ > WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:851 clk_disable+0x24/0x30() > Modules linked in: > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.18.0-09274-g53c5279 #699 > Hardware name: Generic OMAP4 (Flattened Device Tree) > [] (unwind_backtrace) from [] (show_stack+0x10/0x14) > [] (show_stack) from [] (dump_stack+0x80/0x9c) > [] (dump_stack) from [] (warn_slowpath_common+0x78/0xb4) > [] (warn_slowpath_common) from [] (warn_slowpath_null+ 0x1c/0x24) > [] (warn_slowpath_null) from [] (clk_disable+0x24/0x30) > [] (clk_disable) from [] (_disable_clocks+0x18/0x68) > [] (_disable_clocks) from [] (_idle+0x15c/0x240) > [] (_idle) from [] (_setup+0x174/0x22c) > [] (_setup) from [] (omap_hwmod_for_each+0x30/0x5c) > [] (omap_hwmod_for_each) from [] (__omap_hwmod_setup_all+0x30/0x40) > [] (__omap_hwmod_setup_all) from [] (do_one_initcall+0x80/0x1d8) > [] (do_one_initcall) from [] (kernel_init_freeable+0x1f4/0x2cc) > [] (kernel_init_freeable) from [] (kernel_init+0x8/0xe4) > [] (kernel_init) from [] (ret_from_fork+0x14/0x2c) > ---[ end trace f0d1b75165d8ef11 ]--- > clock: dpll_abe_ck failed transition to 'locked' > clock: dpll_abe_ck failed transition to 'locked' > ... > > Tero & Tomi, can you please look into these clock issues above? FYI, looks like merging Mike's pending clk-next to current mainline somehow fixes the clock issues above. It seems the audio changes depended on changes in clk-next? Regards, Tony