summaryrefslogtreecommitdiffstats
path: root/arch/arm/boot/dts/ste-dbx5x0.dtsi
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2017-03-14 10:48:31 +0530
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2017-03-16 00:14:31 +0100
commit19678ffb9fd6f216f530714e62fb469a961874db (patch)
tree4d626647ea5a8b97b839925354f6697243ec90e9 /arch/arm/boot/dts/ste-dbx5x0.dtsi
parent6f19363503541ee6020d35b468a998c213bace36 (diff)
downloadblackbird-obmc-linux-19678ffb9fd6f216f530714e62fb469a961874db.tar.gz
blackbird-obmc-linux-19678ffb9fd6f216f530714e62fb469a961874db.zip
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/boot/dts/ste-dbx5x0.dtsi')
-rw-r--r--arch/arm/boot/dts/ste-dbx5x0.dtsi5
1 files changed, 0 insertions, 5 deletions
diff --git a/arch/arm/boot/dts/ste-dbx5x0.dtsi b/arch/arm/boot/dts/ste-dbx5x0.dtsi
index 82d8c4771293..9eea52013914 100644
--- a/arch/arm/boot/dts/ste-dbx5x0.dtsi
+++ b/arch/arm/boot/dts/ste-dbx5x0.dtsi
@@ -1170,11 +1170,6 @@
status = "disabled";
};
- cpufreq-cooling {
- compatible = "stericsson,db8500-cpufreq-cooling";
- status = "disabled";
- };
-
mcde@a0350000 {
compatible = "stericsson,mcde";
reg = <0xa0350000 0x1000>, /* MCDE */
OpenPOWER on IntegriCloud