Hi, On Monday, January 16, 2012, Antti P Miettinen wrote: > [did not reach linux-pm as I sent to wrong address, sorry for > duplicates] > > The inspiration for this patch series is the N9 CPU frequency boost > upon input events: > > http://www.spinics.net/lists/cpufreq/msg00667.html > > and the related changes in git://codeaurora.org/kernel/msm.git tree. > Those patches modify the ondemand cpufreq governor. This patch series > adds minimum and maximum CPU frequency as PM QoS parameters and > modifies the cpufreq core to enforce the PM QoS limits. If that hasn't been clear enough so far, I'm still not convinced that using PM QoS for that is a good idea. First off, frequency as a unit of throughput is questionable to say the least, because it isn't portable from one system to another. Moreover, even on a given system it isn't particularly clear what the exact correspondence between frequency and throughput actually is. Second, it's not particularly clear what the meaning of the "min" frequency is supposed to be in terms of throughput. Moreover, you make cpufreq export user_policy.min and user_policy.max regardless of the new PM QoS parameters, so it looks like you could use those new attributes to set the min/max as well. Thanks, Rafael -- 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
