| commit | fa29ae5f221860e22a7346d89ae38a28ed104045 | |
| author | Viresh Kumar <viresh.kumar@linaro.org> | |
| Mon, 30 Jan 2017 04:29:57 +0000 (30 09:59 +0530) | ||
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | |
| Fri, 3 Feb 2017 23:05:29 +0000 (4 00:05 +0100) | ||
| tree | 0ddc8a0902ea5503648fe271092aa1dda385ab9f | treesnapshot (tar.gz zip) |
| parent | b12f7a2b01f7adebb9982a6547f4e930914829a9 | commitdiff |
ACPI: processor_perflib: Simplify code and stop using CPUFREQ_START
acpi_processor_ppc_notifier() can live without using CPUFREQ_START
(which is gonna be removed soon), as it is only used while setting
ignore_ppc to 0. This can be done with the help of "ignore_ppc < 0"
check alone. The notifier function anyway ignores all events except
CPUFREQ_ADJUST and dropping CPUFREQ_START wouldn't harm at all.
Once CPUFREQ_START event is removed from the cpufreq core,
acpi_processor_ppc_notifier() will get called only for CPUFREQ_NOTIFY or
CPUFREQ_ADJUST event. Drop the return statement from the first if block
to make sure we don't ignore any such events.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
acpi_processor_ppc_notifier() can live without using CPUFREQ_START
(which is gonna be removed soon), as it is only used while setting
ignore_ppc to 0. This can be done with the help of "ignore_ppc < 0"
check alone. The notifier function anyway ignores all events except
CPUFREQ_ADJUST and dropping CPUFREQ_START wouldn't harm at all.
Once CPUFREQ_START event is removed from the cpufreq core,
acpi_processor_ppc_notifier() will get called only for CPUFREQ_NOTIFY or
CPUFREQ_ADJUST event. Drop the return statement from the first if block
to make sure we don't ignore any such events.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
| drivers/acpi/processor_perflib.c | diffblobblamehistory |