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
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
