From: Zhang Rui <rui.zhang@intel.com>
To: Thomas Renninger <trenn@suse.de>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"clarkt@cnsp.com" <clarkt@cnsp.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPI thermal: Don't invalidate thermal zone if critical trip point is bad
Date: Mon, 22 Feb 2010 09:33:37 +0800 [thread overview]
Message-ID: <1266802417.2608.1463.camel@rzhang1-desktop> (raw)
In-Reply-To: <201002220002.49341.trenn@suse.de>
On Mon, 2010-02-22 at 07:02 +0800, Thomas Renninger wrote:
> On Sunday 21 February 2010 03:51:22 am Zhang Rui wrote:
> ...
> > > @@ -379,17 +379,19 @@ static int acpi_thermal_trips_update(struct
> > > acpi_thermal *tz, int flag) * Below zero (Celsius) values clearly aren't
> > > right for sure.. * ... so lets discard those as invalid.
> > > */
> > > - if (ACPI_FAILURE(status) ||
> > > - tz->trips.critical.temperature <= 2732) {
> > > + if (ACPI_FAILURE(status)) {
> > > + tz->trips.critical.flags.valid = 0;
> > > + ACPI_DEBUG_PRINT((ACPI_DB_INFO,
> > > + "No critical threshold\n"));
> >
> > No critical threshold is also a violation of ACPI spec.
> > what about using FW_BUG here as well?
>
> Could you point me to where this is stated, please.
> I only found Chapter 11.5 (ver. 3.0b):
> Thermal Zone Interface Requirements:
> A thermal zone must contain at least one trip point
> (critical, near critical, active, or passive)
>
> If at another place they state that a critical trip point is
> required, this would contradict with each other.
>
you're right.
I thought I saw such statements somewhere in the ACPI spec but
apparently I'm wrong. Sorry for the noise.
Acked-by: Zhang Rui <rui.zhang@intel.com>
> Thanks,
>
> Thomas
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-02-22 1:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 21:55 [PATCH 1/2] ACPI thermal: Don't invalidate thermal zone if critical trip point is bad Thomas Renninger
2010-02-16 21:55 ` [PATCH 2/2] ACPI thermal: Check for thermal zone requirement Thomas Renninger
2010-02-19 6:39 ` [PATCH 2/2] ACPI thermal: Check for thermal zone requiremen Len Brown
2010-02-19 11:20 ` Thomas Renninger
2010-02-19 16:20 ` Len Brown
2010-02-19 16:37 ` Thomas Renninger
2010-02-20 4:57 ` Len Brown
2010-02-20 9:50 ` Thomas Renninger
2010-02-20 10:15 ` Thomas Renninger
2010-02-19 6:34 ` [PATCH 1/2] ACPI thermal: Don't invalidate thermal zone if critical trip point is bad Len Brown
2010-02-19 7:34 ` Len Brown
2010-02-20 10:20 ` [PATCH] " Thomas Renninger
2010-02-20 10:42 ` Thomas Renninger
2010-02-20 10:44 ` Thomas Renninger
2010-02-21 2:51 ` Zhang Rui
[not found] ` <201002220002.49341.trenn@suse.de>
2010-02-22 1:33 ` Zhang Rui [this message]
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=1266802417.2608.1463.camel@rzhang1-desktop \
--to=rui.zhang@intel.com \
--cc=clarkt@cnsp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=trenn@suse.de \
/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