cpufreq / intel_pstate: Change to disallow module build
authorDirk Brandewie <dirk.brandewie@gmail.com>
Thu, 14 Feb 2013 21:55:34 +0000 (22:55 +0100)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Fri, 15 Feb 2013 21:54:59 +0000 (22:54 +0100)
commitda0d9fda3743769484d3db5a17a121599076e869
treed04920e7892d6588df21e40ffbfa1cea3fc2c3ea
parent191e5edf96dc4939f5db0605cc65de9f4d88d155
cpufreq / intel_pstate: Change to disallow module build

Load order is important in order for intel_pstate to take over as the
default scaling driver from acpi-cpufreq.

If both are built-in, acpi-cpufreq uses late_initcall() and
intel_pstate uses device_initcall() so it will be able to register as
the scaling before acpi-cpufreq for the processors supported by
intel_pstate.

If acpi-cpufreq is built as a module then intel_pstate still gets
first option to become the scaling driver.

Signed-off-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/cpufreq/Kconfig.x86