From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tony Lindgren <tony@atomide.com>
Subject: Re: Cpufreq regression in next-20161207
Date: Wed, 7 Dec 2016 21:52:21 -0800
Message-ID: <20161208055220.GD4264@atomide.com>
References: <20161208045640.GB4264@atomide.com>
 <20161208050739.GE24152@vireshk-i7>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-pm-owner@vger.kernel.org>
Received: from muru.com ([72.249.23.125]:53534 "EHLO muru.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1753408AbcLHFwZ (ORCPT <rfc822;linux-pm@vger.kernel.org>);
        Thu, 8 Dec 2016 00:52:25 -0500
Content-Disposition: inline
In-Reply-To: <20161208050739.GE24152@vireshk-i7>
Sender: linux-pm-owner@vger.kernel.org
List-Id: linux-pm@vger.kernel.org
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>, Stephen Boyd <sboyd@codeaurora.org>, Dave Gerlach <d-gerlach@ti.com>, Nishanth Menon <nm@ti.com>, Tero Kristo <t-kristo@ti.com>, linux-pm@vger.kernel.org, linux-omap@vger.kernel.org

* Viresh Kumar <viresh.kumar@linaro.org> [161207 21:08]:
> 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.

OK good to hear.

> 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.

Hmm good question. Maybe we don't have the regulators configured for
pandaboard?

Regards,

Tony