From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Adam Ford <aford173@gmail.com>, linux-omap@vger.kernel.org
Cc: hns@goldelico.com, tony@atomide.com, neolynx@gmail.com,
letux-kernel@openphoenux.org, linux-kernel@vger.kernel.org,
andreas@kemnade.info, nm@ti.com, adam.ford@logicpd.com
Subject: Re: [RFC] ARM: dts: omap36xx: Enable thermal throttling
Date: Thu, 12 Sep 2019 23:12:18 +0200 [thread overview]
Message-ID: <51bb8890-bfd7-c241-1ce5-151df3a90513@linaro.org> (raw)
In-Reply-To: <20190912183037.18449-1-aford173@gmail.com>
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.
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"?
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
next prev parent reply other threads:[~2019-09-12 21:12 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 [this message]
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
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=51bb8890-bfd7-c241-1ce5-151df3a90513@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 \
/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®