public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Mark <markieb.lists.20090330@gmail.com>
Cc: Clemens Ladisch <clemens@ladisch.de>, linux-kernel@vger.kernel.org
Subject: Re: thermal_zone trip_point_0_temp 200°C
Date: Wed, 06 Jun 2012 09:54:34 +0800	[thread overview]
Message-ID: <1338947674.1492.33.camel@rui.sh.intel.com> (raw)
In-Reply-To: <4FCCC92B.3080809@gmail.com>

On 一, 2012-06-04 at 10:41 -0400, Mark wrote:
> Hi Rui,
> 
> Thanks for writing;
> 
> On 06/03/2012 10:56 PM, Zhang Rui wrote:
> > Usually, the critical trip point value is a hard coded number provided
> > by the BIOS.

This is the ASL code for critical trip point in the ACPI table,

            Name (DCRT, 0x127C)

            Method (_CRT, 0, NotSerialized)
            {
                Return (DCRT)
            }

_CRT, the control method which OS evaluates to get the thermal critical
trip point, returns DCRT, which is a hard coded value 0x127C. And this
equals 473.2 K, or 200C.

So I do not see ACPI thermal does anything wrong here.

> 200° though, possibly the kernel should set a default upper limit, unless there's
> a rational reason

you can use module parameter thermal.crt= to override the critical trip
point.
But I'm not sure if kernel should set a default upper limit or not.
Maybe we need another entry for this laptop in thermal_dmi_table.

> > About fan control, it seems that there is no ACPI FAN on this machine,
> > so the fan may be controlled either by firmware or by some platform
> > specific driver.
> > To make a double check, it would be great if you can refer to
> > http://www.lesswatts.org/projects/acpi/utilities.php
> > to get the acpidump output of this machine.
> >
> > thanks,
> > rui
> 
> I'm tending to a similar conclusion, it looks as though that's generally the case
> with many Aspires; there is a script for poking the hardware registers
> http://code.google.com/p/aceracpi/source/browse/trunk/acer_ec/acer_ec.pl referred
> to at http://www.linuxquestions.org/questions/showthread.php?p=4657451 though it
> sounds a somewhat risky/random business without the manufacturers' specifications
> at the ready
> 
> there are 2-3 symbols in the ACPI that may be relevant, FANG, FANW, possibly
> FANU; I attach the relevant files
> 
FANG/FANW/FANU can be used for fan control?
I do not know what these mean as they are not ACPI pre-defined control
method.
But if all the Aspires machines follow the same rule, then maybe we need
a kernel Acer platform driver that handles this.

thanks,
rui



  reply	other threads:[~2012-06-06  1:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 19:31 thermal_zone trip_point_0_temp 200°C Mark B
2012-06-02  8:34 ` Clemens Ladisch
2012-06-03 18:22   ` Mark
2012-06-04  3:21     ` Zhang Rui
2012-06-04  2:56   ` Zhang Rui
2012-06-04 14:41     ` Mark
2012-06-06  1:54       ` Zhang Rui [this message]
2012-06-15 14:42         ` Mark
2012-06-20  6:54           ` 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=1338947674.1492.33.camel@rui.sh.intel.com \
    --to=rui.zhang@intel.com \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markieb.lists.20090330@gmail.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