cpufreq: Do not allow ->setpolicy drivers to provide ->target
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>
Wed, 19 Mar 2014 11:48:30 +0000 (12:48 +0100)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Wed, 19 Mar 2014 11:48:30 +0000 (12:48 +0100)
cpufreq drivers that provide the ->setpolicy() callback are supposed
to have integrated governors, so they don't need to set ->target()
or ->target_index() and may confuse the core if any of these callbacks
is present.

For this reason, add a check preventing ->setpolicy cpufreq drivers
from registering if they have non-NULL ->target or ->target_index.

Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
drivers/cpufreq/cpufreq.c

Simple merge