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, 20 Jun 2012 14:54:45 +0800 [thread overview]
Message-ID: <1340175285.1682.26.camel@rui.sh.intel.com> (raw)
In-Reply-To: <4FDB49EC.6030806@gmail.com>
On 五, 2012-06-15 at 10:42 -0400, Mark wrote:
> Hi Rui,
>
> thanks for writing; apologies for the delay I've been coping with some bizarre
> communications from AMD who won't even state thermal specifications for the cpu,
> while 'passing the buck' to Acer who are slippery customers — various methods of
> avoiding giving technical support worthy of the name — too :-)
>
> On 06/05/2012 09:54 PM, Zhang Rui wrote:
> > 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.
> thanks, sounds worth a try; at least to prevent a fire :-D
> >
> >> 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.
> I'm simply conjecturing for now, that the letters 'FAN' may be relevant, you're
> the specialist though :-)
No, I only cares about the ACPI pre-defined control methods, which means
their behaviors have been defined in ACPI spec.
Actually, platforms can write whatever AML code, use whatever names, for
their own purpose. so I know nothing more than you on this.
> > thanks,
> > rui
> AMD suggested a channel that would seem designed more for people whose Email
> address is '@acer.com' / '@kernel.org', possibly '@intel.com' than people such as
> me '@gmail.com' :-D
>
> http://support.amd.com/us/contacts/Pages/EmbeddedTechnicalSupport.aspx
>
> My question would be, what *is* the thermal range for the Phenom II N970 Mobile
> CPU, reference HMN970DCR42GM ?
> conspicuously absent from http://products.amd.com/en-us/NotebookCPUDetail.aspx?id=733
>
Sorry, I do not know. I can not help you on this. :(
thanks,
rui
> Aside from the question of whether they've got some technical contact at Acer who
> could verify how — presumably some hardware registers that are somehow accessible
> to the OS — windows seems to manage to keep the CPU relatively cool / fan
> management in the Aspire 5552-7260
>
> Best regards
>
> Mark
>
prev parent reply other threads:[~2012-06-20 6: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
2012-06-15 14:42 ` Mark
2012-06-20 6:54 ` 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=1340175285.1682.26.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