On 22 February 2013 05:05, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > On Monday, February 11, 2013 01:20:00 PM Viresh Kumar wrote: >> This patch is inclined towards providing this infrastructure. Because we are >> required to allocate governor's resources dynamically now, we must do it at >> policy creation and end. And so got CPUFREQ_GOV_POLICY_INIT/EXIT. > > Are those new events NOPs now? No. These are used atleast for ondemand & conservative. >> +#define CPUFREQ_GOV_POLICY_INIT 4 >> +#define CPUFREQ_GOV_POLICY_EXIT 4 > > Why don't you use different values here? > > If you need only one value, one #define should be sufficient. Naah, something happened... I got fixed this locally but couldn't get that into the commit somehow. EXIT should have 5 here. -- 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
