summaryrefslogtreecommitdiffstats
path: root/drivers/cpufreq/intel_pstate.c
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2014-06-13 10:40:32 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2014-06-16 22:33:38 +0200
commit217886d3f3191f1f052e987740ee2bb32a4fd316 (patch)
tree8f031184f4a278d9c3fd5030a27527fc1f0b86bb /drivers/cpufreq/intel_pstate.c
parentLinux 3.16-rc1 (diff)
downloadlinux-217886d3f3191f1f052e987740ee2bb32a4fd316.tar.xz
linux-217886d3f3191f1f052e987740ee2bb32a4fd316.zip
cpufreq: cpufreq-cpu0: fix CPU_THERMAL dependency
5fbfbcd3e842d ("cpufreq: cpufreq-cpu0: remove dependency on THERMAL and REGULATOR") was a little too quick in completely removing the dependency on the THERMAL driver. The problem is that while there are inline wrappers to turn the thermal API calls into empty functions, those do not help if the cpu-thermal driver is a loadable module and cpufreq-cpu0 is builtin. Since CONFIG_CPU_THERMAL is a bool option that decides whether the cpu code is built into the thermal module or not, we have to use a dependency on the thermal driver itself. However, if CPU_THERMAL is disabled, we don't need the dependency, hence the strange '!CPU_THERMAL || THERMAL' construct. Fixes: 5fbfbcd3e842d ("cpufreq: cpufreq-cpu0: remove dependency on THERMAL and REGULATOR") Signed-off-by: Arnd Bergmann <arnd@arndb.de> Tested-by: Viresh Kumar <viresh.kumar@linaro.org> Acked-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/intel_pstate.c')
0 files changed, 0 insertions, 0 deletions