From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Andy Tang <andy.tang@nxp.com>, Shawn Guo <shawnguo@kernel.org>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Leo Li <leoyang.li@nxp.com>,
"edubezval@gmail.com" <edubezval@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"rui.zhang@intel.com" <rui.zhang@intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm64: dts: ls1088a: add one more thermal zone node
Date: Thu, 7 Mar 2019 10:14:44 +0100 [thread overview]
Message-ID: <dc94e884-f5eb-fe07-27ef-6a94c3174acb@linaro.org> (raw)
In-Reply-To: <VI1PR04MB433386B86A5E6AA804E9C3B5F3710@VI1PR04MB4333.eurprd04.prod.outlook.com>
On 04/03/2019 07:46, Andy Tang wrote:
>
>
>> -----Original Message-----
>> From: Shawn Guo <shawnguo@kernel.org>
>> Sent: 2019年3月4日 14:21
>> To: Andy Tang <andy.tang@nxp.com>
>> Cc: Leo Li <leoyang.li@nxp.com>; robh+dt@kernel.org; mark.rutland@arm.com;
>> linux-arm-kernel@lists.infradead.org; devicetree@vger.kernel.org;
>> linux-kernel@vger.kernel.org; linux-pm@vger.kernel.org;
>> daniel.lezcano@linaro.org; rui.zhang@intel.com; edubezval@gmail.com
>> Subject: Re: [PATCH v2] arm64: dts: ls1088a: add one more thermal zone node
>>
>> On Mon, Mar 04, 2019 at 11:21:11AM +0800, Yuantian Tang wrote:
>>> Ls1088a has 2 thermal sensors, core cluster and SoC platform. Core
>>> cluster sensor is used to monitor the temperature of core and SoC
>>> platform is for platform. The current dts only support the first sensor.
>>> This patch adds the second sensor node to dts to enable it.
>>>
>>> Signed-off-by: Yuantian Tang <andy.tang@nxp.com>
>>> ---
>>> v2:
>>> - Add more information about sensors to description
>>> PS: In order to keep consistency to the first thermal-zone node, there
>>> will be "WARNING: line over 80 characters" warnings.
>>>
>>> arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi | 43
>> +++++++++++++++++++++--
>>> 1 files changed, 39 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi
>>> b/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi
>>> index 661137f..9f52bc9 100644
>>> --- a/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi
>>> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi
>>> @@ -129,19 +129,19 @@
>>> };
>>>
>>> thermal-zones {
>>> - cpu_thermal: cpu-thermal {
>>> + ccu {
>>
>> Is this change really necessary? What does 'ccu' stand for?
> I think so. ccu stands for core cluster unit. cpu is too general.
> On some platforms, there are more than one core clusters.
> At least we should change it to "core cluster" if short form is not appropriate.
If the sensor is a the cluster level, 'cluster' is enough. IMHO, no need
to give a description of what contains the cluster, otherwise you will
end up with a 'core-gpu-cluster-l2' name.
>>
>>> polling-delay-passive = <1000>;
>>> polling-delay = <5000>;
>>> thermal-sensors = <&tmu 0>;
>>>
>>> trips {
>>> - cpu_alert: cpu-alert {
>>> + ccu_alert: ccu-alert {
>>> temperature = <85000>;
>>> hysteresis = <2000>;
>>> type = "passive";
>>> };
>>>
>>> - cpu_crit: cpu-crit {
>>> + ccu_crit: ccu-crit {
>>> temperature = <95000>;
>>> hysteresis = <2000>;
>>> type = "critical";
>>> @@ -150,7 +150,42 @@
>>>
>>> cooling-maps {
>>> map0 {
>>> - trip = <&cpu_alert>;
>>> + trip = <&ccu_alert>;
>>> + cooling-device =
>>> + <&cpu0 THERMAL_NO_LIMIT
>> THERMAL_NO_LIMIT>,
>>> + <&cpu1 THERMAL_NO_LIMIT
>> THERMAL_NO_LIMIT>,
>>> + <&cpu2 THERMAL_NO_LIMIT
>> THERMAL_NO_LIMIT>,
>>> + <&cpu3 THERMAL_NO_LIMIT
>> THERMAL_NO_LIMIT>,
>>> + <&cpu4 THERMAL_NO_LIMIT
>> THERMAL_NO_LIMIT>,
>>> + <&cpu5 THERMAL_NO_LIMIT
>> THERMAL_NO_LIMIT>,
>>> + <&cpu6 THERMAL_NO_LIMIT
>> THERMAL_NO_LIMIT>,
>>> + <&cpu7 THERMAL_NO_LIMIT
>> THERMAL_NO_LIMIT>;
>>> + };
>>> + };
>>> + };
>>> +
>>> + plt {
>>
>> What about 'platform-thermal' for node name, platform-alert and platform-crit
>> for trip nodes below?
> OK, will use long name form.
>
> BR,
> Andy
>>
>> Shawn
>>
>>> + polling-delay-passive = <1000>;
>>> + polling-delay = <5000>;
>>> + thermal-sensors = <&tmu 1>;
>>> +
>>> + trips {
>>> + plt_alert: plt-alert {
>>> + temperature = <85000>;
>>> + hysteresis = <2000>;
>>> + type = "passive";
>>> + };
>>> +
>>> + plt_crit: plt-crit {
>>> + temperature = <95000>;
>>> + hysteresis = <2000>;
>>> + type = "critical";
>>> + };
>>> + };
>>> +
>>> + cooling-maps {
>>> + map0 {
>>> + trip = <&plt_alert>;
>>> cooling-device =
>>> <&cpu0 THERMAL_NO_LIMIT
>> THERMAL_NO_LIMIT>,
>>> <&cpu1 THERMAL_NO_LIMIT
>> THERMAL_NO_LIMIT>,
>>> --
>>> 1.7.1
>>>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-07 9:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 3:21 [PATCH v2] arm64: dts: ls1088a: add one more thermal zone node Yuantian Tang
2019-03-04 6:21 ` Shawn Guo
2019-03-04 6:46 ` Andy Tang
2019-03-04 6:53 ` Shawn Guo
2019-03-07 9:14 ` Daniel Lezcano [this message]
2019-03-08 2:07 ` Andy Tang
2019-03-08 9:28 ` Daniel Lezcano
2019-03-08 9:57 ` Andy Tang
2019-03-20 8:18 ` Shawn Guo
2019-03-20 8:44 ` Andy Tang
2019-03-20 14:49 ` Shawn Guo
2019-03-21 1:05 ` Andy Tang
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=dc94e884-f5eb-fe07-27ef-6a94c3174acb@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=andy.tang@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=shawnguo@kernel.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).