linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linaro.org>
To: mark.hambleton@broadcom.com, mark.brown@linaro.org,
	eduardo.valentin@ti.com, mporter@linaro.org,
	lsk-interest@linaro.org, linaro-kernel@linaro.org
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Russell King" <linux@arm.linux.org.uk>,
	linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, "Alex Shi" <alex.shi@linaro.org>
Subject: [PATCH 10/19] arm: dts: add cooling properties on omap4430 cpu node
Date: Tue, 25 Mar 2014 18:49:23 +0800	[thread overview]
Message-ID: <1395744572-20014-11-git-send-email-alex.shi@linaro.org> (raw)
In-Reply-To: <1395744572-20014-1-git-send-email-alex.shi@linaro.org>

From: Eduardo Valentin <eduardo.valentin@ti.com>

OMAP4430 devices can reach high temperatures and thus
needs to have cpufreq-cooling on systems running on it.

This patch adds the required cooling device properties
so that cpufreq-cpu0 driver loads the cooling device.

Cc: "Benoît Cousson" <bcousson@baylibre.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org
Cc: devicetree-discuss@lists.ozlabs.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com>
(cherry picked from commit 72af5e6d0c3e01655c1c1fc7c7ca94a2b663611e)

Signed-off-by: Alex Shi <alex.shi@linaro.org>
---
 arch/arm/boot/dts/omap443x.dtsi | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/arch/arm/boot/dts/omap443x.dtsi b/arch/arm/boot/dts/omap443x.dtsi
index cccf39a..d2deba0 100644
--- a/arch/arm/boot/dts/omap443x.dtsi
+++ b/arch/arm/boot/dts/omap443x.dtsi
@@ -22,6 +22,11 @@
 				1008000 1375000
 			>;
 			clock-latency = <300000>; /* From legacy driver */
+
+			/* cooling options */
+			cooling-min-level = <0>;
+			cooling-max-level = <3>;
+			#cooling-cells = <2>; /* min followed by max */
 		};
 	};
 };
-- 
1.8.1.2

  parent reply	other threads:[~2014-03-25 10:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1395744572-20014-1-git-send-email-alex.shi@linaro.org>
2014-03-25 10:49 ` [PATCH 09/19] arm: dts: add omap4 CPU thermal data Alex Shi
2014-03-25 10:49 ` Alex Shi [this message]
2014-05-06 15:20   ` [PATCH 10/19] arm: dts: add cooling properties on omap4430 cpu node Tony Lindgren
2014-03-25 10:49 ` [PATCH 11/19] arm: dts: add cooling properties on omap4460 " Alex Shi
2014-03-25 10:49 ` [PATCH 12/19] arm: dts: add omap5 GPU thermal data Alex Shi
2014-03-25 10:49 ` [PATCH 13/19] arm: dts: add omap5 CORE " Alex Shi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1395744572-20014-11-git-send-email-alex.shi@linaro.org \
    --to=alex.shi@linaro.org \
    --cc=bcousson@baylibre.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=eduardo.valentin@ti.com \
    --cc=linaro-kernel@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=lsk-interest@linaro.org \
    --cc=mark.brown@linaro.org \
    --cc=mark.hambleton@broadcom.com \
    --cc=mporter@linaro.org \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).