It was pointed out in today's technical syncup that sched-dvfs should rely on its own static key, and that static key should not indicate a dependency on EAS.
The static key was named sched_energy_freq. I've renamed/shortened it to sched_freq. I also think we should try and use this name for the feature in general since I believe less people are familiar with the term/acronym DVFS. A git grep -i dvfs suggests it's almost exclusively an ARM term, at least as far as the kernel source goes, with a little usage in sound codecs and GPU.
If anyone has a better name or concerns please share...
thanks, Steve
On Fri, Nov 6, 2015 at 9:06 AM, Steve Muckle steve.muckle@linaro.org wrote:
It was pointed out in today's technical syncup that sched-dvfs should rely on its own static key, and that static key should not indicate a dependency on EAS.
The static key was named sched_energy_freq. I've renamed/shortened it to sched_freq. I also think we should try and use this name for the feature in general since I believe less people are familiar with the term/acronym DVFS. A git grep -i dvfs suggests it's almost exclusively an ARM term, at least as far as the kernel source goes, with a little usage in sound codecs and GPU.
If anyone has a better name or concerns please share...
One other name could be sched_cpufreq - since it involves the tighter coupling between the scheduler and cpufreq subsystem*. I don't have a strong feeling either way though. The name could be changed by the community during review.
* And we don't expect this code to deal with scaling the GPU and other peripherals.
-
Amit Kucheria -
Steve Muckle