diff options
| author | Viresh Kumar <viresh.kumar@linaro.org> | 2017-03-14 10:48:31 +0530 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2017-03-16 00:14:31 +0100 |
| commit | 19678ffb9fd6f216f530714e62fb469a961874db (patch) | |
| tree | 4d626647ea5a8b97b839925354f6697243ec90e9 /arch/arm/mach-orion5x/Kconfig | |
| parent | 6f19363503541ee6020d35b468a998c213bace36 (diff) | |
cpufreq: dbx500: Manage cooling device from cpufreq driver
The best place to register the CPU cooling device is from the cpufreq
driver as we would know if all the resources are already available or
not. That's what is done for the cpufreq-dt.c driver as well.
The cpu-cooling driver for dbx500 platform was just (un)registering
with the thermal framework and that can be handled easily by the cpufreq
driver as well and in proper sequence as well.
Get rid of the cooling driver and its its users and manage everything
from the cpufreq driver instead.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Tested-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'arch/arm/mach-orion5x/Kconfig')
0 files changed, 0 insertions, 0 deletions