[PATCH] cpufreq: Set policy to non-NULL only after all hotplug online work is done
From: viresh.kumar@linaro.org (Viresh Kumar)
Date: 2014-02-24 08:46:03
Also in:
linux-arm-msm, linux-pm, lkml
On 24 February 2014 14:11, [off-list ref] wrote:
I just replied to the other email. I think I answered both your questions there. Sorry about mixing up CPU and policy. In my case, each CPU is independently scalable -- so for now take CPU == policy. I'll fix it up once we agree on the fix.
But why do you say this then?
quoted
quoted
In this specific case, CPU0 set's CPU1's policy->governor in cpufreq_init_policy() to NULL while CPU1 is using the policy->governor in __cpufreq_governor().