From: j-keerthy@ti.com (Keerthy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/7] ARM: OMAP5: Thermal: Add slope and offset values
Date: Wed, 1 Mar 2017 15:59:45 +0530 [thread overview]
Message-ID: <1488364190-23488-3-git-send-email-j-keerthy@ti.com> (raw)
In-Reply-To: <1488364190-23488-1-git-send-email-j-keerthy@ti.com>
Currently the slope and offset values for calculating the
hot spot temperature of a particular thermal zone is part
of driver data. Pass them here instead and obtain the values
while of node parsing.
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 222155c..eaff2a5 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -1127,6 +1127,15 @@
&cpu_thermal {
polling-delay = <500>; /* milliseconds */
+ coefficients = <65 (-1791)>;
};
/include/ "omap54xx-clocks.dtsi"
+
+&gpu_thermal {
+ coefficients = <117 (-2992)>;
+};
+
+&core_thermal {
+ coefficients = <0 2000>;
+};
--
1.9.1
next prev parent reply other threads:[~2017-03-01 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 10:29 [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree Keerthy
2017-03-01 10:29 ` [PATCH 1/7] ARM: DRA7: Thermal: Add slope and offset values Keerthy
2017-03-01 10:29 ` Keerthy [this message]
2017-03-01 10:29 ` [PATCH 3/7] ARM: OMAP443x: " Keerthy
2017-03-01 10:29 ` [PATCH 4/7] ARM: OMAP4460: " Keerthy
2017-03-01 10:29 ` [PATCH 5/7] thermal: ti-soc-thermal: Fetch slope and offset from DT Keerthy
2017-03-01 10:29 ` [PATCH 6/7] thermal: ti-soc-thermal: Remove redundant constants Keerthy
2017-03-01 10:29 ` [PATCH 7/7] thermal: ti-soc-thermal: Remove redundant code Keerthy
2017-03-06 18:42 ` [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree Tony Lindgren
2017-03-07 7:13 ` Keerthy
2017-03-07 15:12 ` Tony Lindgren
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=1488364190-23488-3-git-send-email-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).