On 02/15/2016 01:36 PM, Tony Lindgren wrote:
* Rafael J. Wysocki <rafael@xxxxxxxxxx> [160215 12:39]:
On Mon, Feb 15, 2016 at 8:58 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote:
* Guenter Roeck <linux@xxxxxxxxxxxx> [160215 11:41]:
On 02/15/2016 11:01 AM, Tony Lindgren wrote:
https://kernelci.org/boot/all/job/next/kernel/next-20160215/
The SMP ones seem to fail with some regulator issues?
There is another problem, introduced with 6a0712f6f199e ("PM / OPP: Add
dev_pm_opp_set_rate()"). The kernelci boot log for next-20160212:omap3-overo-tobi
and others experience that problem.
Essentially, the code now assumes that a CPU clock always has a voltage
regulator attached to it, which is not correct. I sent out a patch to fix
that problem a minute ago.
Yes that fixed it thanks.
Can you please also check if this alternative fix from Viresh works:
https://patchwork.kernel.org/patch/8316611/
Yes that one too seems to fix the issue on SMP systems for
me:
Tested-by: Tony Lindgren <tony@xxxxxxxxxxx>
Same here.
Tested-by: Guenter Roeck <linux@xxxxxxxxxxxx>
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
