Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932626AbbBBQWG (ORCPT ); Mon, 2 Feb 2015 11:22:06 -0500 Received: from smtp2.ore.mailhop.org ([54.186.57.195]:52470 "EHLO smtp2.ore.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932542AbbBBQWE (ORCPT ); Mon, 2 Feb 2015 11:22:04 -0500 X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 104.193.169.186 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX18Svy/Eu0xu8ZCmEKMv7OiD Date: Mon, 2 Feb 2015 08:18:59 -0800 From: Tony Lindgren To: Mike Turquette Cc: Stephen Boyd , Tomeu Vizoso , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org Subject: Re: Clock Regression in next-20150130 caused by cb75a8fcd14e Message-ID: <20150202161858.GH16250@atomide.com> References: <20150131010443.GE16250@atomide.com> <20150201232636.421.58980@quantum> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150201232636.421.58980@quantum> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1541 Lines: 42 * Mike Turquette [150201 15:29]: > Quoting Tony Lindgren (2015-01-30 17:04:44) > > 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/<20150131013158.GA4323@codeaurora.org> > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/