From: Tony Lindgren <tony@atomide.com>
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
Subject: Re: Cpufreq regression in next-20161207
Date: Wed, 7 Dec 2016 21:52:21 -0800 [thread overview]
Message-ID: <20161208055220.GD4264@atomide.com> (raw)
In-Reply-To: <20161208050739.GE24152@vireshk-i7>
* 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
next prev parent reply other threads:[~2016-12-08 5:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 4:56 Cpufreq regression in next-20161207 Tony Lindgren
2016-12-08 5:07 ` Viresh Kumar
2016-12-08 5:52 ` Tony Lindgren [this message]
2016-12-08 5:57 ` Viresh Kumar
2016-12-08 6:04 ` Tony Lindgren
2016-12-08 8:54 ` Tero Kristo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161208055220.GD4264@atomide.com \
--to=tony@atomide.com \
--cc=d-gerlach@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sboyd@codeaurora.org \
--cc=t-kristo@ti.com \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox