From: Amjad Ouled-Ameur <aouledameur@baylibre.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] arm64: dts: mediatek: mt8183: disable thermal zones without trips.
Date: Thu, 6 Oct 2022 13:08:19 +0200 [thread overview]
Message-ID: <cdebdf53-d691-41b6-bb8e-f66bb6f56e56@baylibre.com> (raw)
In-Reply-To: <17f3fd40-70c1-2e8d-8002-dfe9690aed88@linaro.org>
Hi Daniel,
Thank you for your feedback.
On 10/4/22 12:47, Daniel Lezcano wrote:
>
> Hi Amjad,
>
> On 04/10/2022 12:11, Amjad Ouled-Ameur wrote:
>> Thermal zones without trip point are not registered by thermal core.
>>
>> tzts1 ~ tzts6 zones of mt8183 were intially introduced for test-purpose
>> only.
>>
>> Disable the zones above and keep only cpu_thermal enabled.
>
> It does not make sense to disable the thermal zones. Either the thermal zones are needed or they are not. Keeping them for debug purpose is not desired.
As Matthias Brugger mentioned in previous versions, DTS should describe the HW as it is, the sensors are in the HW.
>
> Alternatively to removal, you can:
>
> - remove 'sustainable-power'
> - add a passive trip point, optionally a hot trip point and a critical trip point
Why removing "sustainable-power" instead of simply disabling the device ? Especially that, if a user needs to use the sensor
in the future, they might not be able to find the right sustainable-power ; thus I think it should remain the way it is.
As to adding tripping points, MediaTek does not have ones to add for now for those sensors.
Regards,
Amjad
>
> The passive trip point will allow the userspace to set a value in order to get notified about the devices temperature (writable trip point). The hot temperature will send a notification to userspace so it can take a last chance decision to drop the temperature before the critical temperature.
>
> The passive trip point temperature could be a high temperature.
>
> The mitigation is also managed from userspace as a whole.
>
>
>> Signed-off-by: Amjad Ouled-Ameur <aouledameur@baylibre.com>
>> ---
>> arch/arm64/boot/dts/mediatek/mt8183.dtsi | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
>> index 9d32871973a2..53f7a0fbaa88 100644
>> --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
>> +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
>> @@ -1191,6 +1191,7 @@ tzts1: tzts1 {
>> polling-delay = <0>;
>> thermal-sensors = <&thermal 1>;
>> sustainable-power = <5000>;
>> + status = "disabled";
>> trips {};
>> cooling-maps {};
>> };
>> @@ -1200,6 +1201,7 @@ tzts2: tzts2 {
>> polling-delay = <0>;
>> thermal-sensors = <&thermal 2>;
>> sustainable-power = <5000>;
>> + status = "disabled";
>> trips {};
>> cooling-maps {};
>> };
>> @@ -1209,6 +1211,7 @@ tzts3: tzts3 {
>> polling-delay = <0>;
>> thermal-sensors = <&thermal 3>;
>> sustainable-power = <5000>;
>> + status = "disabled";
>> trips {};
>> cooling-maps {};
>> };
>> @@ -1218,6 +1221,7 @@ tzts4: tzts4 {
>> polling-delay = <0>;
>> thermal-sensors = <&thermal 4>;
>> sustainable-power = <5000>;
>> + status = "disabled";
>> trips {};
>> cooling-maps {};
>> };
>> @@ -1227,6 +1231,7 @@ tzts5: tzts5 {
>> polling-delay = <0>;
>> thermal-sensors = <&thermal 5>;
>> sustainable-power = <5000>;
>> + status = "disabled";
>> trips {};
>> cooling-maps {};
>> };
>> @@ -1236,6 +1241,7 @@ tztsABB: tztsABB {
>> polling-delay = <0>;
>> thermal-sensors = <&thermal 6>;
>> sustainable-power = <5000>;
>> + status = "disabled";
>> trips {};
>> cooling-maps {};
>> };
>
>
next prev parent reply other threads:[~2022-10-06 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 10:11 [PATCH v3] arm64: dts: mediatek: mt8183: disable thermal zones without trips Amjad Ouled-Ameur
2022-10-04 10:47 ` Daniel Lezcano
2022-10-06 11:08 ` Amjad Ouled-Ameur [this message]
2022-10-06 11:29 ` Daniel Lezcano
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=cdebdf53-d691-41b6-bb8e-f66bb6f56e56@baylibre.com \
--to=aouledameur@baylibre.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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