From: Keerthy <j-keerthy@ti.com>
To: <tony@atomide.com>, <edubezval@gmail.com>
Cc: <rui.zhang@intel.com>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<robh+dt@kernel.org>, <t-kristo@ti.com>, <j-keerthy@ti.com>
Subject: [PATCH v2 0/8] thermal: ti-soc-thermal: Migrate slope/offset data to device tree
Date: Thu, 9 Mar 2017 13:35:54 +0530 [thread overview]
Message-ID: <1489046762-11288-1-git-send-email-j-keerthy@ti.com> (raw)
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.
Tested for the slope and constant values on DRA7-EVM, OMAP3-BEAGLE.
Changes in v2:
* Added OMAP3 changes along with DRA7/OMAP4/OMAP5.
Keerthy (8):
arm: dts: omap3: Add cpu_thermal zone
ARM: DRA7: Thermal: Add slope and offset values
ARM: OMAP5: Thermal: Add slope and offset values
ARM: OMAP443x: Thermal: Add slope and offset values
ARM: OMAP4460: Thermal: Add slope and offset values
thermal: ti-soc-thermal: Fetch slope and offset from DT
thermal: ti-soc-thermal: Remove redundant constants
thermal: ti-soc-thermal: Remove redundant code
arch/arm/boot/dts/dra7.dtsi | 17 +++
arch/arm/boot/dts/omap3-cpu-thermal.dtsi | 20 +++
arch/arm/boot/dts/omap34xx.dtsi | 8 +-
arch/arm/boot/dts/omap36xx.dtsi | 8 +-
arch/arm/boot/dts/omap443x.dtsi | 4 +
arch/arm/boot/dts/omap4460.dtsi | 4 +
arch/arm/boot/dts/omap5.dtsi | 9 ++
.../thermal/ti-soc-thermal/dra752-thermal-data.c | 10 --
.../thermal/ti-soc-thermal/omap3-thermal-data.c | 4 -
.../thermal/ti-soc-thermal/omap4-thermal-data.c | 6 -
.../thermal/ti-soc-thermal/omap5-thermal-data.c | 4 -
drivers/thermal/ti-soc-thermal/ti-bandgap.h | 4 -
drivers/thermal/ti-soc-thermal/ti-thermal-common.c | 158 +--------------------
drivers/thermal/ti-soc-thermal/ti-thermal.h | 16 ---
14 files changed, 71 insertions(+), 201 deletions(-)
create mode 100644 arch/arm/boot/dts/omap3-cpu-thermal.dtsi
--
1.9.1
next reply other threads:[~2017-03-09 8:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 8:05 Keerthy [this message]
2017-03-09 8:05 ` [PATCH v2 1/8] arm: dts: omap3: Add cpu_thermal zone Keerthy
2017-03-09 8:05 ` [PATCH v2 2/8] ARM: DRA7: Thermal: Add slope and offset values Keerthy
2017-03-09 8:05 ` [PATCH v2 3/8] ARM: OMAP5: " Keerthy
2017-03-29 4:33 ` Eduardo Valentin
2017-03-30 3:27 ` Keerthy
2017-03-09 8:05 ` [PATCH v2 4/8] ARM: OMAP443x: " Keerthy
2017-03-09 8:05 ` [PATCH v2 5/8] ARM: OMAP4460: " Keerthy
2017-03-09 8:06 ` [PATCH v2 6/8] thermal: ti-soc-thermal: Fetch slope and offset from DT Keerthy
2017-03-09 8:06 ` [PATCH v2 7/8] thermal: ti-soc-thermal: Remove redundant constants Keerthy
2017-03-09 8:06 ` [PATCH v2 8/8] thermal: ti-soc-thermal: Remove redundant code Keerthy
2017-03-22 3:42 ` [PATCH v2 0/8] thermal: ti-soc-thermal: Migrate slope/offset data to device tree Keerthy
2017-03-23 20:52 ` Tony Lindgren
2017-03-24 3:26 ` Keerthy
2017-03-24 14:26 ` Tony Lindgren
2017-03-29 4:37 ` Eduardo Valentin
2017-03-30 3:29 ` Keerthy
2017-03-30 4:46 ` Eduardo Valentin
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=1489046762-11288-1-git-send-email-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=edubezval@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=t-kristo@ti.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;
as well as URLs for NNTP newsgroup(s).