From: Lukasz Majewski <l.majewski@samsung.com>
To: linux-pm@vger.kernel.org
Subject: Re: [PATCH] thermal: core: ignore invalid trip temperature
Date: Thu, 13 Nov 2014 10:23:11 +0100 [thread overview]
Message-ID: <20141113102311.64331d60@amdc2363> (raw)
In-Reply-To: <1415835809-23376-1-git-send-email-srinivas.pandruvada@linux.intel.com>
Hi Srinivas,
> Ignore invalid trip temperature less or equal to zero. Some
> buggy systems have invalid trips, causing system shutdown.
>
> Signed-off-by: Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> Acked-by: Zhang Rui
> <rui.zhang@intel.com> ---
> drivers/thermal/thermal_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/thermal/thermal_core.c
> b/drivers/thermal/thermal_core.c index 9bf10aa..fbf301a 100644
> --- a/drivers/thermal/thermal_core.c
> +++ b/drivers/thermal/thermal_core.c
> @@ -368,7 +368,7 @@ static void handle_critical_trips(struct
> thermal_zone_device *tz, tz->ops->get_trip_temp(tz, trip, &trip_temp);
>
> /* If we have not crossed the trip_temp, we do not care. */
> - if (tz->temperature < trip_temp)
> + if (trip_temp <= 0 || tz->temperature < trip_temp)
To be honest, I regard this as a feature :-), not bug.
In this way I know that on some systems the regulator for thermal unit
is not enabled (which results in read temp of 0xFF).
I'd prefer to keep this as is.
> return;
>
> trace_thermal_zone_trip(tz, trip, trip_type);
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
next prev parent reply other threads:[~2014-11-13 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 23:43 [PATCH] thermal: core: ignore invalid trip temperature Srinivas Pandruvada
2014-11-13 9:23 ` Lukasz Majewski [this message]
[not found] ` <1415892544.4581.17.camel@spandruv-hsb-test>
[not found] ` <20141114125054.64e93e5b@amdc2363>
2014-11-15 17:24 ` Srinivas Pandruvada
2014-11-20 2:25 ` Zhang Rui
2014-11-20 10:25 ` Lukasz Majewski
2014-11-20 17:13 ` Srinivas Pandruvada
2014-11-25 5:34 ` Zhang Rui
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=20141113102311.64331d60@amdc2363 \
--to=l.majewski@samsung.com \
--cc=linux-pm@vger.kernel.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