From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] imx: thermal: use CPU temperature grade info for thresholds
Date: Sun, 24 May 2015 10:48:37 +0800 [thread overview]
Message-ID: <20150524024836.GA3264@dragon> (raw)
In-Reply-To: <1432251947-13335-1-git-send-email-tharvey@gateworks.com>
On Thu, May 21, 2015 at 04:45:47PM -0700, Tim Harvey wrote:
> The IMX6Q/IMX6DL SoC's have a 2-bit temperature grade stored in OTP which
> is valid for all IMX6 SoC's (despite the fact that the IMXSDLRM and
> IMXSXRM do not document this - this has been proven via tests as well as
> verified by Freescale FAE).
>
> Instead of assuming a fixed 85C for passive cooling threshold and 105C for
> critical use the thermal grade for these configurations.
>
> We will set the critical to maxT - 5C and passive to maxT - 10C.
>
> Cc: Anson Huang <b20788@freescale.com>
> Cc: Fabio Estevam <fabio.estevam@freescale.com>
> Cc: Eduardo Valentin <edubezval@gmail.com>
> Cc: Zhang Rui <rui.zhang@intel.com>
> Signed-off-by: Tim Harvey <tharvey@gateworks.com>
Acked-by: Shawn Guo <shawn.guo@linaro.org>
next prev parent reply other threads:[~2015-05-24 2:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 16:02 [PATCH] imx: thermal: use CPU temperature grade info for thresholds Tim Harvey
2015-05-11 12:22 ` Shawn Guo
2015-05-11 12:26 ` Fabio Estevam
2015-05-11 13:31 ` Tim Harvey
2015-05-12 1:32 ` Eduardo Valentin
2015-05-11 18:55 ` Fabio Estevam
2015-05-20 22:08 ` Tim Harvey
2015-05-21 23:45 ` [PATCH v2] " Tim Harvey
2015-05-24 2:48 ` Shawn Guo [this message]
2015-05-24 5:19 ` Jon Nettleton
2015-05-26 21:24 ` Tim Harvey
2015-05-27 6:08 ` Jon Nettleton
2015-07-28 14:50 ` Tim Harvey
2015-07-28 15:01 ` Jon Nettleton
2015-07-28 16:10 ` Jon Nettleton
2015-07-28 16:12 ` Jon Nettleton
2015-07-30 7:19 ` [PATCH] " Jon Nettleton
2015-10-13 14:16 ` Tim Harvey
2015-10-13 14:16 ` Tim Harvey
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=20150524024836.GA3264@dragon \
--to=shawn.guo@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.