On Wed, Mar 12, 2014 at 4:57 AM, Rafael J. Wysocki <rjw@xxxxxxxxxxxxx> wrote: >> Well, ->setpolicy drivers are a special case anyway, so we can simply skip the >> current frequency updates in __cpufreq_add_dev() and cpufreq_update_policy() >> for them. > > In other words, we can do something like in the patch below I suppose? I don't think its a good idea to handle ->setpolicy specially here. Zero shouldn't be allowed as a return value of any online CPU. And doesn't matter at all with ->setpolicy or ->target. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
