Re: [PATCH] cpufreq: Set policy to non-NULL only after all hotplug online work is done
From: Viresh Kumar <viresh.kumar@linaro.org>
Date: 2014-02-25 14:40:57
Also in:
linux-arm-kernel, linux-arm-msm, lkml
On 25 February 2014 18:34, Rafael J. Wysocki [off-list ref] wrote:
Well, that depends on what the current users expect it to look like initially. It should be initialized to the point in which all of them can handle it correctly.
Exactly.
That's not going to work in at least some cases anyway, because for some types of HW we simply can't retrieve the current frequency in a non-racy way.
I agree. But this is all that we can guarantee here :)