From: Caesar Wang <wxt@rock-chips.com>
To: edubezval@gmail.com
Cc: Heiko Stuebner <heiko@sntech.de>,
dianders@chromium.org, briannorris@google.com,
smbarber@google.com, linux-rockchip@lists.infradead.org,
dmitry.torokhov@gmail.com, huangtao@rock-chips.com,
eddie.cai@rock-chips.com, Caesar Wang <wxt@rock-chips.com>,
linux-pm@vger.kernel.org, Keerthy <j-keerthy@ti.com>,
linux-kernel@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
linux-omap@vger.kernel.org
Subject: [PATCH 0/4] Thermal: Support for hardware-tracked trip points
Date: Mon, 25 Apr 2016 11:02:43 +0800 [thread overview]
Message-ID: <1461553367-24744-1-git-send-email-wxt@rock-chips.com> (raw)
The history patches come from Mikko and Sascha.
http://thread.gmane.org/gmane.linux.power-management.general/59451
Now, I pick them up to continue upstream.
Nevermind!
Tis series adds support for hardware trip points. It picks up earlier
work from Mikko Perttunen. Mikko implemented hardware trip points as part
of the device tree support. It was suggested back then to move the
functionality to the thermal core instead of putting more code into the
device tree support. This series does exactly that.
This series patches rebase the conflicts.
Note that the hardware-tracked trip points are very well tested currently.
Verified and tested on https://github.com/Caesar-github/rockchip/tree/wip/fixes-thermal-0425
That's based on linux-kernel 20160422.
[ 0.000000] Linux version 4.6.0-rc4-next-20160422-00016-g0ac0bfb-dirty
Sascha Hauer (4):
thermal: Add support for hardware-tracked trip points
thermal: of: implement .set_trips for device tree thermal zones
thermal: streamline get_trend callbacks
thermal: bang-bang governor: act on lower trip boundary
drivers/thermal/gov_bang_bang.c | 2 +-
drivers/thermal/of-thermal.c | 23 ++++++-----
drivers/thermal/thermal_core.c | 48 ++++++++++++++++++++++
drivers/thermal/ti-soc-thermal/ti-thermal-common.c | 25 ++++-------
include/linux/thermal.h | 9 +++-
5 files changed, 78 insertions(+), 29 deletions(-)
--
1.9.1
next reply other threads:[~2016-04-25 3:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 3:02 Caesar Wang [this message]
2016-04-25 3:02 ` [PATCH 1/4] thermal: Add support for hardware-tracked trip points Caesar Wang
2016-04-27 21:48 ` Eduardo Valentin
[not found] ` <20160427214843.GA6438-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2016-05-03 6:19 ` Caesar Wang
2016-05-03 9:25 ` Caesar Wang
2016-04-25 3:02 ` [PATCH 2/4] thermal: of: implement .set_trips for device tree thermal zones Caesar Wang
2016-04-27 21:52 ` Eduardo Valentin
2016-05-03 6:32 ` Caesar Wang
[not found] ` <1461553367-24744-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-04-25 3:02 ` [PATCH 3/4] thermal: streamline get_trend callbacks Caesar Wang
2016-04-25 3:02 ` [PATCH 4/4] thermal: bang-bang governor: act on lower trip boundary Caesar Wang
2016-04-27 21:54 ` Eduardo Valentin
2016-04-28 6:30 ` Sascha Hauer
[not found] ` <20160428063018.GX7860-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-04-28 14:50 ` 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=1461553367-24744-1-git-send-email-wxt@rock-chips.com \
--to=wxt@rock-chips.com \
--cc=briannorris@google.com \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eddie.cai@rock-chips.com \
--cc=edubezval@gmail.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=rui.zhang@intel.com \
--cc=smbarber@google.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).