From: caesar.upstream@gmail.com (Caesar Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: rockchip: override thermal settings on veyron-speedy
Date: Mon, 30 Nov 2015 22:00:41 +0800 [thread overview]
Message-ID: <565C5689.60208@gmail.com> (raw)
In-Reply-To: <2523702.pCcOIjvoVs@diego>
Hi Heiko,
? 2015?11?30? 21:14, Heiko St?bner ??:
> According to a commit on the ChromeOS kernel, the temperature of the Speedy
> surface is over skin temperature spec. So adjust the thermal settings
> to mimic the ChromeOS tree to stay within these spec limits.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@collabora.com>
> ---
> arch/arm/boot/dts/rk3288-veyron-speedy.dts | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm/boot/dts/rk3288-veyron-speedy.dts b/arch/arm/boot/dts/rk3288-veyron-speedy.dts
> index a7ea7d0..b34a7b5 100644
> --- a/arch/arm/boot/dts/rk3288-veyron-speedy.dts
> +++ b/arch/arm/boot/dts/rk3288-veyron-speedy.dts
> @@ -88,6 +88,14 @@
> };
> };
>
> +&cpu_alert0 {
> + temperature = <65000>;
> +};
> +
> +&cpu_alert1 {
> + temperature = <70000>;
> +};
> +
Yep, as the mass of thermal data from OEM with all kinds of testing.
The 65/70 degree is very suit for speedy. (e.g.: Power, Performance).
So, feel free add my tag: :-)
Reviewed-by: Caesar Wang <wxt@rock-chips.com>
> &rk808 {
> pinctrl-names = "default";
> pinctrl-0 = <&pmic_int_l>;
next prev parent reply other threads:[~2015-11-30 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 13:13 [PATCH 1/2] ARM: dts: rockchip: update the thermal management on rk3288 Heiko Stübner
2015-11-30 13:14 ` [PATCH 2/2] ARM: dts: rockchip: override thermal settings on veyron-speedy Heiko Stübner
2015-11-30 14:00 ` Caesar Wang [this message]
2015-11-30 14:17 ` [PATCH 1/2] ARM: dts: rockchip: update the thermal management on rk3288 Heiko Stübner
2015-12-01 13:39 ` Heiko Stübner
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=565C5689.60208@gmail.com \
--to=caesar.upstream@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).