cpufreq : powernv: Report Pmax throttling if capped below nominal frequency
authorShilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Mon, 14 Sep 2015 08:31:47 +0000 (14:01 +0530)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Sat, 26 Sep 2015 01:03:06 +0000 (03:03 +0200)
commitd43b1b6f8e5b3219d4d02ea7fadcf67fecf78b1a
treedc6d5fe08aeb72fe6ce8ae78f9d95d6df430c33b
parenta35fc5a33b62a6c658b8ffe7544c966c1776d128
cpufreq : powernv: Report Pmax throttling if capped below nominal frequency

Log a 'critical' message if the max frequency is reduced below nominal
frequency. We already log 'info' message if the max frequency is
capped below turbo frequency. CPU should guarantee atleast nominal
frequency, but not turbo frequency in all system configurations and
environments. So report the pmax throttling with severity when Pmax is
dipped below nominal frequency.

Signed-off-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/cpufreq/powernv-cpufreq.c