From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Adam Ford" <aford173@gmail.com>,
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: Wed, 18 Sep 2019 11:37:47 +0200 [thread overview]
Message-ID: <caf10e4e-c688-cdb7-7d0d-7a030923a194@linaro.org> (raw)
In-Reply-To: <20190918092418.que4c5jpcn2dcavx@vireshk-mac-ubuntu>
On 18/09/2019 11:24, Viresh Kumar wrote:
> On 13-09-19, 00:33, Daniel Lezcano wrote:
>>
>> 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?
>
> Sorry but I am not able to understand what's not supported by thermal framework
> here and what can I do to help :)
The solution of preventing running above the 90°C by changing the OPPs
is fine and works. It is a way of workaround the spec.
But AFAIU, the specs of the board say the OPPs 800MHz and 1GHz are only
permitted during an amount of time above 90°C which makes the constraint
inverted and recall somehow the 'turbo-mode' description:
"
- turbo-mode: Marks the OPP to be used only for turbo modes. Turbo mode
is available on some platforms, where the device can run over its
operating frequency for a short duration of time limited by the device's
power, current and thermal limits.
"
This is where I thought you can give an input.
--
<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-18 9:37 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
2019-09-18 9:24 ` Viresh Kumar
2019-09-18 9:36 ` H. Nikolaus Schaller
2019-09-18 9:37 ` Daniel Lezcano [this message]
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=caf10e4e-c688-cdb7-7d0d-7a030923a194@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®