diff options
| author | Yinghai Lu <yinghai@kernel.org> | 2013-09-20 10:43:56 -0700 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2013-09-25 03:19:09 +0200 |
| commit | 8a61e12e84597b5f8155ac91b44dea866ccfaac2 (patch) | |
| tree | ad5b14b1f1ad4acd0fc19e61ba34091d32ccc3b5 /Kconfig | |
| parent | 4a10c2ac2f368583138b774ca41fac4207911983 (diff) | |
| download | op-kernel-dev-8a61e12e84597b5f8155ac91b44dea866ccfaac2.zip op-kernel-dev-8a61e12e84597b5f8155ac91b44dea866ccfaac2.tar.gz | |
acpi-cpufreq: skip loading acpi_cpufreq after intel_pstate
If the hw supports intel_pstate and acpi_cpufreq, intel_pstate will
get loaded first.
acpi_cpufreq_init() will call acpi_cpufreq_early_init()
and that will allocate perf data and init those perf data in ACPI core,
(that will cover all CPUs). But later it will free them as
cpufreq_register_driver(acpi_cpufreq) will fail as intel_pstate is
already registered
Use cpufreq_get_current_driver() to check if we can skip the
acpi_cpufreq loading.
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions
