On 24 February 2014 14:11, <skan...@codeaurora.org> 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? >>> 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(). -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
