From: Randy Li <randy.li@rock-chips.com>
To: Caesar Wang <sasukewxt@163.com>
Cc: ayaka <ayaka@soulik.info>, Caesar Wang <wxt@rock-chips.com>,
linux-pm@vger.kernel.org, briannorris@chromium.org,
linux-kernel@vger.kernel.org, smbarber@chromium.org,
edubezval@gmail.com, linux-rockchip@lists.infradead.org,
rui.zhang@intel.com
Subject: Re: [PATCH v4 0/5] thermal: fixes the rockchip thermal
Date: Tue, 3 Jan 2017 09:13:59 +0800 [thread overview]
Message-ID: <9ee3d263-8de3-eb95-034d-774ae216329f@rock-chips.com> (raw)
In-Reply-To: <c2b13d66-e89e-02c8-3a68-6eb57627aaf2@163.com>
On 01/03/2017 09:02 AM, Caesar Wang wrote:
>
> 在 2017年01月03日 07:57, Randy Li 写道:
>>
>> On 01/02/2017 09:16 PM, Caesar Wang wrote:
>>> 在 2016年12月31日 00:11, ayaka 写道:
>>>>
>>>> BTW, Caesar have you ever met this at RK3288 at booting time?
>>>> [ 8.430582] thermal thermal_zone1: critical temperature
>>>> reached(125 C),shutting down
>>>> [ 8.439038] thermal thermal_zone2: critical temperature
>>>> reached(125 C),shutting down
>>>> [ 8.456344] thermal thermal_zone1: critical temperature
>>>> reached(125 C),shutting down
>>>> [ 8.465298] thermal thermal_zone2: critical temperature
>>>> reached(125 C),shutting down
>>>
>>> 125C? the thermal zone isn't the upstream kernel, what's the kernel
>>> version?
>> They have been merged into the linux-next.
>
> Really?
> I saw the 90 degree is the critical temperature on rk3288 dts .
Yes I do.
> kernel$ vi arch/arm/boot/dts/rk3288.dtsi
> cpu_crit: cpu_crit {
> temperature = <90000>; /* millicelsius */
> hysteresis = <2000>; /* millicelsius */
> type = "critical";
> };
>
>>> Anyway, look like, the TSHUT issue. Do you have the below patches
>>> for your linux kernel?
>>> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/380446.html
>>>
>> No, could you resubmit those patches ?
>
> These patches had merged for upstream.
Sorry, it is my fault, I mistake that commit. Those patches are merged
in next-20161224. I would bring a board for you later.
>
> -Caesar
>
>
--
Randy Li
The third produce department
===========================================================================
This email message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message. [Fuzhou Rockchip Electronics, INC. China mainland]
===========================================================================
next prev parent reply other threads:[~2017-01-03 1:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 11:05 [PATCH v4 0/5] thermal: fixes the rockchip thermal Caesar Wang
2016-12-12 11:05 ` [PATCH v4 1/5] thermal: rockchip: improve conversion error messages Caesar Wang
2016-12-12 11:05 ` [PATCH v4 2/5] thermal: rockchip: don't pass table structs by value Caesar Wang
[not found] ` <1481540735-12710-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-12-12 11:05 ` [PATCH v4 3/5] thermal: rockchip: fixes invalid temperature case Caesar Wang
2016-12-12 11:05 ` [PATCH v4 4/5] thermal: rockchip: optimize the conversion table Caesar Wang
2016-12-12 11:05 ` [PATCH v4 5/5] thermal: rockchip: handle set_trips without the trip points Caesar Wang
2016-12-30 16:11 ` [PATCH v4 0/5] thermal: fixes the rockchip thermal ayaka
2017-01-02 13:16 ` Caesar Wang
[not found] ` <8bdcea3e-0f06-da29-cb17-6b258440900a-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-01-02 23:57 ` Randy Li
2017-01-03 1:02 ` Caesar Wang
2017-01-03 1:13 ` Randy Li [this message]
[not found] ` <9ee3d263-8de3-eb95-034d-774ae216329f-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-01-03 16:30 ` ayaka
2017-01-14 16:54 ` Eduardo Valentin
2017-01-15 3:35 ` ayaka
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=9ee3d263-8de3-eb95-034d-774ae216329f@rock-chips.com \
--to=randy.li@rock-chips.com \
--cc=ayaka@soulik.info \
--cc=briannorris@chromium.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=rui.zhang@intel.com \
--cc=sasukewxt@163.com \
--cc=smbarber@chromium.org \
--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