From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Adam Ford <aford173@gmail.com>, Viresh Kumar <viresh.kumar@linaro.org>
Cc: Linux-OMAP <linux-omap@vger.kernel.org>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
"Tony Lindgren" <tony@atomide.com>,
"André Roth" <neolynx@gmail.com>,
"Discussions about the Letux Kernel"
<letux-kernel@openphoenux.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andreas Kemnade" <andreas@kemnade.info>,
"Nishanth Menon" <nm@ti.com>, "Adam Ford" <adam.ford@logicpd.com>
Subject: Re: [RFC] ARM: dts: omap36xx: Enable thermal throttling
Date: Fri, 13 Sep 2019 00:33:40 +0200 [thread overview]
Message-ID: <2ef812a4-2f2d-b2e2-9fa4-080775e24bc8@linaro.org> (raw)
In-Reply-To: <CAHCN7xKjwkJHysSkNymF=sw6KuS=FqbapuRFZODuj6E_hmRG1A@mail.gmail.com>
Hi Adam,
On 12/09/2019 23:19, Adam Ford wrote:
> On Thu, Sep 12, 2019 at 4:12 PM Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>>
>> On 12/09/2019 20:30, Adam Ford wrote:
>>> The thermal sensor in the omap3 family isn't accurate, but it's
>>> better than nothing. The various OPP's enabled for the omap3630
>>> support up to OPP1G, however the datasheet for the DM3730 states
>>> that OPP130 and OPP1G are not available above TJ of 90C.
>>>
>>> This patch configures the thermal throttling to limit the
>>> operating points of the omap3630 to Only OPP50 and OPP100 if
>>> the thermal sensor reads a value above 90C.
Oh, that's a very interesting use case.
AFAICT the thermal framework is not designed to deal with this
situation. I agree this setup may work (even if I'm not convinced about
the stability of the whole).
May be Viresh can help for the cpufreq side?
>> Out of curiosity, what are the OPP50 and OPP100 mentioned above? and
>> what does mean "OPP130 and OPP1G are not available above TJ of 90C"?
>>
> OPP130 is the 800 MHz and OPP1G is 1GHz operating point.
> The 90C is the max junction temperature. When the temperature exceeds
> 90C, the processor is not designed to operate at 800+ MHz. The
> statement itself is a direct quote from the public datasheet for the
> dm3730, Table 4-19.
> The datasheet is: http://www.ti.com/lit/ds/symlink/dm3730.pdf
It is ambiguous how it is stated:
"OPP130 and OPP1G are not available above TJ of 90C"
that can be interpreted the OPP is disabled by the hardware, no?
> The operating points were updated in [1], but they haven't yet been
> fully applied yet, but during the discussion, the question came about
> regarding how to limit the speed at high temp, so that's why this
> patch was done.
>
> [1] - https://patchwork.kernel.org/patch/11141643/
I see, you switched to opp-v2.
Thanks for the detailed answer.
>> I don't see the connection between these OPP names and the definition in
>> the DT.
>>
>>> Signed-off-by: Adam Ford <aford173@gmail.com>
>>>
>>> diff --git a/arch/arm/boot/dts/omap36xx.dtsi b/arch/arm/boot/dts/omap36xx.dtsi
>>> index 4bb4f534afe2..58b9d347019f 100644
>>> --- a/arch/arm/boot/dts/omap36xx.dtsi
>>> +++ b/arch/arm/boot/dts/omap36xx.dtsi
>>> @@ -25,6 +25,7 @@
>>>
>>> vbb-supply = <&abb_mpu_iva>;
>>> clock-latency = <300000>; /* From omap-cpufreq driver */
>>> + #cooling-cells = <2>;
>>> };
>>> };
>>>
>>> @@ -195,6 +196,31 @@
>>> };
>>> };
>>>
>>> +&cpu_thermal {
>>> + cpu_trips: trips {
>>> + /* OPP130 and OPP1G are not available above TJ of 90C. */
>>> + cpu_alert0: cpu_alert {
>>> + temperature = <90000>; /* millicelsius */
>>> + hysteresis = <2000>; /* millicelsius */
>>> + type = "passive";
>>> + };
>>> +
>>> + cpu_crit: cpu_crit {
>>> + temperature = <125000>; /* millicelsius */
>>> + hysteresis = <2000>; /* millicelsius */
>>> + type = "critical";
>>> + };
>>> + };
>>> +
>>> + cpu_cooling_maps: cooling-maps {
>>> + map0 {
>>> + trip = <&cpu_alert0>;
>>> + /* Only allow OPP50 and OPP100 */
>>> + cooling-device = <&cpu 0 1>;
>>> + };
>>> + };
>>> +};
>>> +
>>> /* OMAP3630 needs dss_96m_fck for VENC */
>>> &venc {
>>> clocks = <&dss_tv_fck>, <&dss_96m_fck>;
>>>
>>
>>
>> --
>> <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
>>
--
<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
next prev parent reply other threads:[~2019-09-12 22:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 18:30 Adam Ford
2019-09-12 21:12 ` Daniel Lezcano
2019-09-12 21:19 ` Adam Ford
2019-09-12 22:33 ` Daniel Lezcano [this message]
2019-09-18 9:24 ` Viresh Kumar
2019-09-18 9:36 ` H. Nikolaus Schaller
2019-09-18 9:37 ` Daniel Lezcano
2019-09-13 6:55 ` H. Nikolaus Schaller
2019-09-13 11:07 ` Adam Ford
2019-09-13 13:28 ` Adam Ford
2019-09-13 13:32 ` H. Nikolaus Schaller
2019-09-13 14:05 ` Adam Ford
2019-09-13 14:24 ` H. Nikolaus Schaller
2019-09-13 15:01 ` Adam Ford
2019-09-13 15:09 ` H. Nikolaus Schaller
2019-09-13 16:35 ` Adam Ford
2019-09-13 16:42 ` Adam Ford
2019-09-13 16:51 ` H. Nikolaus Schaller
2019-09-13 17:18 ` Daniel Lezcano
2019-09-13 18:46 ` Adam Ford
2019-09-13 20:01 ` Adam Ford
2019-09-13 20:11 ` Daniel Lezcano
2019-09-13 20:34 ` H. Nikolaus Schaller
2019-09-13 21:01 ` Adam Ford
2019-09-14 9:53 ` 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=2ef812a4-2f2d-b2e2-9fa4-080775e24bc8@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=adam.ford@logicpd.com \
--cc=aford173@gmail.com \
--cc=andreas@kemnade.info \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=neolynx@gmail.com \
--cc=nm@ti.com \
--cc=tony@atomide.com \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®