From mboxrd@z Thu Jan 1 00:00:00 1970 From: Viresh Kumar Subject: Re: Cpufreq regression in next-20161207 Date: Thu, 8 Dec 2016 10:37:39 +0530 Message-ID: <20161208050739.GE24152@vireshk-i7> References: <20161208045640.GB4264@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-pf0-f182.google.com ([209.85.192.182]:34197 "EHLO mail-pf0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750729AbcLHFHn (ORCPT ); Thu, 8 Dec 2016 00:07:43 -0500 Received: by mail-pf0-f182.google.com with SMTP id c4so81520359pfb.1 for ; Wed, 07 Dec 2016 21:07:43 -0800 (PST) Content-Disposition: inline In-Reply-To: <20161208045640.GB4264@atomide.com> Sender: linux-pm-owner@vger.kernel.org List-Id: linux-pm@vger.kernel.org To: Tony Lindgren Cc: "Rafael J. Wysocki" , Stephen Boyd , Dave Gerlach , Nishanth Menon , Tero Kristo , linux-pm@vger.kernel.org, linux-omap@vger.kernel.org Hi Tony, On 07-12-16, 20:56, Tony Lindgren wrote: > Hi, > > Looks like commit ef3caabee969 ("PM / OPP: Don't assume platform doesn't > have regulators") caused a regression in Linux next-20161207 for at least > omap4 pandaboard. We now hit kernel BUG at drivers/cpufreq/cpufreq.c:1235. > > Any ideas? I saw similar regression for Tegra and the offending commit is now dropped from pm/linux-next. So linux-next should be fine after fetching it today. But just for my understanding, who is doing voltage scaling for OMAP4 then? The cpufreq-dt driver will only frequency scaling, as it fails to find a regulator for the CPUs. -- viresh