summaryrefslogtreecommitdiff
path: root/Documentation/admin-guide/pm/cpufreq.rst
diff options
context:
space:
mode:
authorQuentin Perret <qperret@google.com>2020-06-29 11:24:59 +0300
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2020-07-02 14:03:30 +0300
commit10dd8573b09e84b81539d939d55ebdb6a36c5f3a (patch)
treeda0835325c0c812473ac33dddda211c869802407 /Documentation/admin-guide/pm/cpufreq.rst
parent8cc46ae565c393f77417cb9530b1265eb50f5d2e (diff)
downloadlinux-10dd8573b09e84b81539d939d55ebdb6a36c5f3a.tar.xz
cpufreq: Register governors at core_initcall
Currently, most CPUFreq governors are registered at the core_initcall time when the given governor is the default one, and the module_init time otherwise. In preparation for letting users specify the default governor on the kernel command line, change all of them to be registered at the core_initcall unconditionally, as it is already the case for the schedutil and performance governors. This will allow us to assume that builtin governors have been registered before the built-in CPUFreq drivers probe. And since all governors have similar init/exit patterns now, introduce two new macros, cpufreq_governor_{init,exit}(), to factorize the code. Acked-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Quentin Perret <qperret@google.com> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> [ rjw: Changelog ] Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'Documentation/admin-guide/pm/cpufreq.rst')
0 files changed, 0 insertions, 0 deletions