summaryrefslogtreecommitdiff
path: root/fs/minix
diff options
context:
space:
mode:
authorLenny Szubowicz <lszubowi@redhat.com>2014-11-13 13:51:52 -0500
committerSasha Levin <sasha.levin@oracle.com>2015-08-27 13:25:58 -0400
commit57a45cb53cba2261d7e909f944a3ddd4d61e8ac2 (patch)
tree6913cc92967c695aee3af4ff2f96af37aa9e76dd /fs/minix
parent33fdddbdf9bf8f0200739483c4b562b895c11274 (diff)
downloadlinux-rt-57a45cb53cba2261d7e909f944a3ddd4d61e8ac2.tar.gz
cpufreq: pcc: Enable autoload of pcc-cpufreq for ACPI processors
[ Upstream commit 7e7e8fe69820c6fa31395dbbd8e348e3c69cd2a9 ] The pcc-cpufreq driver is not automatically loaded on systems where the platform's power management setting requires this driver. Instead, on those systems no CPU frequency driver is registered and active. Make the autoloading matching criteria for loading the pcc-cpufreq driver the same as done in acpi-cpufreq by commit c655affbd524d01 ("ACPI / cpufreq: Add ACPI processor device IDs to acpi-cpufreq"). x86 CPU frequency drivers are now typically autoloaded by specifying MODULE_DEVICE_TABLE entries and x86cpu model specific matching. But pcc-cpufreq was omitted when acpi-cpufreq and other drivers were changed to use this approach. Both acpi-cpufreq and pcc-cpufreq depend on a distinct and mutually exclusive set of ACPI methods which are not directly tied to specific processor model numbers. Both of these drivers have init routines which look for their required ACPI methods. As a result, only the appropriate driver registers as the cpu frequency driver and the other one ends up being unloaded. Tested on various systems where acpi-cpufreq, intel_pstate, and pcc-cpufreq are the expected cpu frequency drivers. Signed-off-by: Lenny Szubowicz <lszubowi@redhat.com> Signed-off-by: Joseph Szczypek <joseph.szczypek@hp.com> Reported-by: Trinh Dao <trinh.dao@hp.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Diffstat (limited to 'fs/minix')
0 files changed, 0 insertions, 0 deletions