From: Caesar Wang <caesar.wang@rock-chips.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: heiko@sntech.de, rui.zhang@intel.com, edubezval@gmail.com,
zyf@rock-chips.com, dianders@chromium.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
cf@rock-chips.com, dbasehore@chromium.org,
huangtao@rock-chips.com, cjf@rock-chips.com,
zhengsq@rock-chips.com
Subject: Re: [PATCH v13 4/5] ARM: dts: add main Thermal info to rk3288
Date: Fri, 24 Oct 2014 09:08:52 +0800 [thread overview]
Message-ID: <5449A6A4.3070608@rock-chips.com> (raw)
In-Reply-To: <20141024004625.GD9463@dtor-ws>
Dmitry,
在 2014/10/24 8:46, Dmitry Torokhov 写道:
> Hi Caesar,
>
> On Thu, Oct 23, 2014 at 05:40:06PM +0800, Caesar Wang wrote:
>> This patch is depend on rk3288-thermal.dtsi,or
>> it will compile error.
>>
>> If the temperature over a period of time High,over 120C
>> the resulting TSHUT gave CRU module,let it reset
>> the entire chip,or via GPIO give PMIC.
>>
>> Signed-off-by: Caesar Wang <caesar.wang@rock-chips.com>
>> ---
>> arch/arm/boot/dts/rk3288.dtsi | 21 +++++++++++++++++++++
>> 1 file changed, 21 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
>> index cb18bb4..85fc17a 100644
>> --- a/arch/arm/boot/dts/rk3288.dtsi
>> +++ b/arch/arm/boot/dts/rk3288.dtsi
>> @@ -15,6 +15,7 @@
>> #include <dt-bindings/interrupt-controller/arm-gic.h>
>> #include <dt-bindings/pinctrl/rockchip.h>
>> #include <dt-bindings/clock/rk3288-cru.h>
>> +#include <dt-bindings/thermal/thermal.h>
>> #include "skeleton.dtsi"
>>
>> / {
>> @@ -66,6 +67,7 @@
>> 216000 900000
>> 126000 900000
>> >;
>> + #cooling-cells = <2>; /* min followed by max */
>> clock-latency = <40000>;
>> clocks = <&cru ARMCLK>;
>> };
>> @@ -346,6 +348,19 @@
>> status = "disabled";
>> };
>>
>> + tsadc: tsadc@ff280000 {
>> + compatible = "rockchip,rk3288-tsadc";
>> + reg = <0xff280000 0x100>;
>> + interrupts = <GIC_SPI 37 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&cru SCLK_TSADC>, <&cru PCLK_TSADC>;
>> + clock-names = "tsadc", "apb_pclk";
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&otp_out>;
>> + #thermal-sensor-cells = <1>;
>> + hw-shut-temp = <120000>;
> I do not think this is a good value. You have (in the other DTS file)
> passive trip point at 80 and critical (which should result in orderly
> shutdown) at 125. But here you define hardware-controlled shutdown at
> 120C, which is backwards. You should have:
>
> passive <= critical <= hardware
Hmmm....
but, the system will shutdown when temperature over critial value,
there is no chance of triggering the TSHUT.
If the temperature over a period of time High,as we know,
the resulting TSHUT gave CRU module,let it hot-reset the entire chip,
or via GPIO give PMIC cold-reset the entire chip.
> Thanks.
>
--
Best regards,
Caesar
next prev parent reply other threads:[~2014-10-24 1:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 9:40 [PATCH v13 0/5] Rockchip soc thermal driver Caesar Wang
2014-10-23 9:40 ` [PATCH v13 1/5] thermal: rockchip: add driver for thermal Caesar Wang
2014-10-24 0:55 ` Dmitry Torokhov
2014-10-24 8:21 ` Dmitry Torokhov
2014-10-24 8:35 ` Caesar Wang
2014-10-23 9:40 ` [PATCH v13 2/5] dt-bindings: document Rockchip thermal Caesar Wang
2014-10-23 9:40 ` [PATCH v13 3/5] ARM: dts: add RK3288 Thermal data Caesar Wang
2014-10-24 0:48 ` Dmitry Torokhov
2014-10-24 2:19 ` Caesar Wang
2014-10-23 9:40 ` [PATCH v13 4/5] ARM: dts: add main Thermal info to rk3288 Caesar Wang
2014-10-24 0:46 ` Dmitry Torokhov
2014-10-24 1:08 ` Caesar Wang [this message]
2014-10-24 1:37 ` Dmitry Torokhov
2014-10-24 2:06 ` Caesar Wang
2014-10-24 2:32 ` Dmitry Torokhov
2014-10-24 3:21 ` Caesar Wang
2014-10-24 8:17 ` Dmitry Torokhov
2014-10-23 9:40 ` [PATCH v13 5/5] ARM: dts: enable Thermal on rk3288-evb board Caesar Wang
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=5449A6A4.3070608@rock-chips.com \
--to=caesar.wang@rock-chips.com \
--cc=cf@rock-chips.com \
--cc=cjf@rock-chips.com \
--cc=dbasehore@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=edubezval@gmail.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=rui.zhang@intel.com \
--cc=zhengsq@rock-chips.com \
--cc=zyf@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