From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: "Daniel Lezcano" <daniel.lezcano@linaro.org>,
linux-arm-kernel@lists.infradead.org,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Rob Herring" <robh@kernel.org>,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: renesas: r8a779g3: Update thermal trip points on V4H Sparrow Hawk
Date: Mon, 18 Aug 2025 10:59:31 +0200 [thread overview]
Message-ID: <CAMuHMdXHhwWyzKN7LrVFhyiQQSOpCa_MjJMUH5tOqiDdEwM2fg@mail.gmail.com> (raw)
In-Reply-To: <154ea688-8e06-40c6-944c-084fb9d5ce26@mailbox.org>
Hi Marek,
On Fri, 15 Aug 2025 at 01:36, Marek Vasut <marek.vasut@mailbox.org> wrote:
> On 8/14/25 5:50 PM, Geert Uytterhoeven wrote:
> > On Wed, 6 Aug 2025 at 17:23, Marek Vasut <marek.vasut@mailbox.org> wrote:
> >> On 8/6/25 11:35 AM, Geert Uytterhoeven wrote:
> >>>> +/* THS sensor in SoC near CA76 cores does more progressive cooling. */
> >>>> +&sensor_thermal_ca76 {
> >>>> + critical-action = "shutdown";
> >>>> +
> >>>> + cooling-maps {
> >>>> + /*
> >>>> + * The cooling-device minimum and maximum parameters inversely
> >>>> + * match opp-table-0 {} node entries in r8a779g0.dtsi, in other
> >>>> + * words, 0 refers to 1.8 GHz OPP and 4 refers to 500 MHz OPP.
> >>>> + * This is because they refer to cooling levels, where maximum
> >>>> + * cooling level happens at 500 MHz OPP, when the CPU core is
> >>>> + * running slowly and therefore generates least heat.
> >>>
> >>> That applies to cooling-device = <&a76_[0-3] ...>...
> >>
> >> Do you want me to add this line into the comment ?
> >
> > I don't think that is really needed (see below)
> >
> >>>> + */
> >>>> + map0 {
> >>>> + /* At 68C, inhibit 1.7 GHz and 1.8 GHz modes */
> >>>> + trip = <&sensor3_passive_low>;
> >>>> + cooling-device = <&a76_0 2 4>;
> >>>> + contribution = <128>;
> >>>> + };
> >>>> +
> >>>> + map1 {
> >>>> + /* At 72C, inhibit 1.5 GHz mode */
> >>>> + trip = <&sensor3_passive_mid>;
> >>>> + cooling-device = <&a76_0 3 4>;
> >>>> + contribution = <256>;
> >>>> + };
> >>>> +
> >>>> + map2 {
> >>>> + /* At 76C, start injecting idle states */
> >>>> + trip = <&sensor3_passive_hi>;
> >>>> + cooling-device = <&a76_0_thermal_idle 0 80>,
> >>>> + <&a76_1_thermal_idle 0 80>,
> >>>> + <&a76_2_thermal_idle 0 80>,
> >>>> + <&a76_3_thermal_idle 0 80>;
> >>>
> >>> ... but what do "0 80" refer to? I couldn't find in the thermal-idle
> >>> bindings what exactly are the minimum and maximum cooling states here.
> >>
> >> The comments in drivers/thermal/cpuidle_cooling.c clarify that, it is
> >> the idle injection rate in percent, in this case the cooling can inject
> >> idle states up to 80% of time.
> >
> > OK, so I will add "(0-80%)" to the idle states comment, and sort
> > the nodes while queuing in renesas-devel for v6.18.
> I sent a V3 to make this more official. I hope that helps.
Thanks, I took v3 instead.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2025-08-18 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 10:01 [PATCH] arm64: dts: renesas: r8a779g3: Update thermal trip points on V4H Sparrow Hawk Marek Vasut
2025-06-26 21:41 ` Niklas Söderlund
2025-06-29 22:32 ` Marek Vasut
2025-06-30 8:13 ` Niklas Söderlund
2025-08-06 9:35 ` Geert Uytterhoeven
2025-08-06 15:23 ` Marek Vasut
2025-08-14 15:50 ` Geert Uytterhoeven
2025-08-14 23:36 ` Marek Vasut
2025-08-18 8:59 ` Geert Uytterhoeven [this message]
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=CAMuHMdXHhwWyzKN7LrVFhyiQQSOpCa_MjJMUH5tOqiDdEwM2fg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut@mailbox.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=robh@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).