From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree
Date: Mon, 6 Mar 2017 10:42:16 -0800 [thread overview]
Message-ID: <20170306184215.GO20572@atomide.com> (raw)
In-Reply-To: <1488364190-23488-1-git-send-email-j-keerthy@ti.com>
* Keerthy <j-keerthy@ti.com> [170301 02:31]:
> 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.
>
> Keerthy (7):
> 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
Are the dts changes safe for me to pick separately into
omap-for-v4.12/dt?
Regards,
Tony
next prev parent reply other threads:[~2017-03-06 18:42 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 ` [PATCH 2/7] ARM: OMAP5: " Keerthy
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 ` Tony Lindgren [this message]
2017-03-07 7:13 ` [PATCH 0/7] thermal: ti-soc-thermal: Migrate slope/offset data to device tree 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=20170306184215.GO20572@atomide.com \
--to=tony@atomide.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).