cpufreq: Avoid false-positive WARN_ON()s in cpufreq_update_policy()
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>
Tue, 28 Jun 2016 01:29:29 +0000 (03:29 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 10 Aug 2016 10:54:46 +0000 (12:54 +0200)
commit4be5c33b5e44b3beb78100a94192e51d597e16a1
tree4fba59d0428739243c6c901f7997f4522e83e9b6
parent8b592e2ac932c3fa110fc820e9b2c1dc6b67df9c
cpufreq: Avoid false-positive WARN_ON()s in cpufreq_update_policy()

commit 742c87bf27d3b715820da6f8a81d6357adbf18f8 upstream.

CPU notifications from the firmware coming in when cpufreq is
suspended cause cpufreq_update_current_freq() to return 0 which
triggers the WARN_ON() in cpufreq_update_policy() for no reason.

Avoid that by checking cpufreq_suspended before calling
cpufreq_update_current_freq().

Fixes: c9d9c929e674 (cpufreq: Abort cpufreq_update_current_freq() for cpufreq_suspended set)
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/cpufreq/cpufreq.c