From: Caesar Wang <caesar.upstream@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Brian Norris <briannorris@chromium.org>,
Eduardo Valentin <edubezval@gmail.com>,
Sascha Hauer <kernel@pengutronix.de>,
huangtao@rock-chips.com, Wei Ni <wni@nvidia.com>,
Heiko Stuebner <heiko@sntech.de>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
dianders@chromium.org, linux-rockchip@lists.infradead.org,
eddie.cai@rock-chips.com, smbarber@google.com,
Paul Walmsley <pwalmsley@nvidia.com>,
Zhang Rui <rui.zhang@intel.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
Caesar Wang <wxt@rock-chips.com>
Subject: Re: [PATCH 7/9] thermal: of: Add support for hardware-tracked trip points
Date: Fri, 22 Apr 2016 18:17:54 +0800 [thread overview]
Message-ID: <5719FA52.4070506@gmail.com> (raw)
In-Reply-To: <20160422054147.GI21638@pengutronix.de>
Hi Sascha,
>>>> These are still the newest patches. I won't have any resources in the
>>>> near future for continuing the work on them, so feel free to pick them
>>>> up. There hasn't been much discussion around these patches which was the
>>>> reason I abandoned them.
Okay.
I start to pick them up and do some tests in my github.
https://github.com/Caesar-github/rockchip/commits/wip/support-thermal-hardware-trip-points
_
Caesar
>
> Sascha
>
>
--
Thanks,
Caesar
next prev parent reply other threads:[~2016-04-22 10:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 3:35 [PATCH 0/9] thermal: rockchip: Support rk3366/rk3399 SoCS and fixes the driver Caesar Wang
2016-04-18 3:35 ` [PATCH 1/9] thermal: rockchip: disable thermal->clk in err case Caesar Wang
2016-04-18 3:35 ` [PATCH 2/9] thermal: rockchip: fixes the code_to_temp for tsadc driver Caesar Wang
2016-04-18 3:35 ` [PATCH 3/9] thermal: rockchip: update the tsadc table for rk3399 Caesar Wang
2016-04-18 3:35 ` [PATCH 4/9] thermal: rockchip: handle the power sequence for tsadc controller Caesar Wang
2016-04-27 23:48 ` Eduardo Valentin
[not found] ` <57216C65.5040501@gmail.com>
2016-04-28 15:04 ` Eduardo Valentin
2016-05-03 2:27 ` Caesar Wang
2016-04-18 3:35 ` [PATCH 5/9] thermal: rockchip: Support RK3366 SoCs in the thermal driver Caesar Wang
2016-04-18 3:35 ` [PATCH 6/9] thermal: rockchip: add the notes for better reading Caesar Wang
2016-04-18 3:35 ` [PATCH 7/9] thermal: of: Add support for hardware-tracked trip points Caesar Wang
2016-04-20 23:48 ` Eduardo Valentin
2016-04-21 1:12 ` Brian Norris
2016-04-22 1:54 ` Caesar Wang
2016-04-22 5:41 ` Sascha Hauer
2016-04-22 10:17 ` Caesar Wang [this message]
2016-04-27 21:50 ` Eduardo Valentin
2016-04-18 3:36 ` [PATCH 8/9] thermal: rockchip: add the set_trips function Caesar Wang
2016-04-27 23:52 ` [PATCH 0/9] thermal: rockchip: Support rk3366/rk3399 SoCS and fixes the driver 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=5719FA52.4070506@gmail.com \
--to=caesar.upstream@gmail.com \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=eddie.cai@rock-chips.com \
--cc=edubezval@gmail.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mperttunen@nvidia.com \
--cc=pwalmsley@nvidia.com \
--cc=rui.zhang@intel.com \
--cc=s.hauer@pengutronix.de \
--cc=smbarber@google.com \
--cc=wni@nvidia.com \
--cc=wxt@rock-chips.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).