From: Keerthy <j-keerthy@ti.com>
To: <tony@atomide.com>, <edubezval@gmail.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <linux@arm.linux.org.uk>,
<galak@codeaurora.org>, <ijc+devicetree@hellion.org.uk>,
<mark.rutland@arm.com>, Keerthy <j-keerthy@ti.com>
Subject: [PATCH] arm: dts: AM57XX: Correct the thermal thresholds
Date: Mon, 8 Feb 2016 15:15:05 +0530 [thread overview]
Message-ID: <1454924705-8382-1-git-send-email-j-keerthy@ti.com> (raw)
The thermal threholds for am57xx are different from that of dra7.
Correcting the thresholds for the same.
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
Depends on: https://lkml.org/lkml/2016/2/8/90
arch/arm/boot/dts/am57xx-beagle-x15.dts | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
Index: linux/arch/arm/boot/dts/am57xx-beagle-x15.dts
===================================================================
--- linux.orig/arch/arm/boot/dts/am57xx-beagle-x15.dts 2016-02-08 14:57:05.514959101 +0530
+++ linux/arch/arm/boot/dts/am57xx-beagle-x15.dts 2016-02-08 14:57:05.510959168 +0530
@@ -825,3 +825,27 @@
status = "okay";
};
};
+
+&cpu_alert0 {
+ temperature = <90000>; /* milliCelsius */
+};
+
+&cpu_crit {
+ temperature = <105000>; /* milliCelsius */
+};
+
+&gpu_crit {
+ temperature = <105000>; /* milliCelsius */
+};
+
+&core_crit {
+ temperature = <105000>; /* milliCelsius */
+};
+
+&dspeve_crit {
+ temperature = <105000>; /* milliCelsius */
+};
+
+&iva_crit {
+ temperature = <105000>; /* milliCelsius */
+};
next reply other threads:[~2016-02-08 9:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 9:45 Keerthy [this message]
2016-02-09 22:09 ` Eduardo Valentin
2016-02-09 22:16 ` Nishanth Menon
2016-02-12 22:23 ` Tony Lindgren
2016-02-12 22:30 ` Nishanth Menon
2016-02-12 22:41 ` Tony Lindgren
2016-02-15 4:27 ` Keerthy
2016-02-15 15:49 ` Nishanth Menon
2016-02-15 16:13 ` Keerthy
2016-02-15 17:25 ` Nishanth Menon
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=1454924705-8382-1-git-send-email-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--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=mark.rutland@arm.com \
--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
all inboxes | Powered by JetHome®