linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cesar Eduardo Barros <cesarb@cesarb.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	Joe Perches <joe@perches.com>, Matthew Garrett <mjg@redhat.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] intel_ips: quieten "power or thermal limit exceeded" messages
Date: Mon, 30 Aug 2010 18:42:55 -0300	[thread overview]
Message-ID: <4C7C25DF.3070401@cesarb.net> (raw)
In-Reply-To: <20100830092958.1c50c8cb@jbarnes-desktop>

Em 30-08-2010 13:29, Jesse Barnes escreveu:
> It's possible that the main issue here is bad thermal limits.  There's
> obviously a relationship between power and thermal output, but the
> driver tries to monitor both.  However it's up to the BIOS to provide
> the driver with accurate thermal limits, as well as accurate power
> limits.  The power limits sound reasonable at 25W, thus the
> informational output about 35W vs 25W (35W is what the MCP can handle,
> but some platforms are designed to handle less, so they clamp it down a
> bit).  But the temp limits look all wrong.  I'll see if I can find info
> on getting better data into the driver...

If you need more information from this laptop (dmidecode, ACPI AML, 
etc), just ask.

-- 
Cesar Eduardo Barros
cesarb@cesarb.net
cesar.barros@gmail.com

  reply	other threads:[~2010-08-30 21:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25  0:48 intel ips: CPU TDP doesn't match expected value Cesar Eduardo Barros
2010-08-25  1:37 ` Jesse Barnes
2010-08-26 23:29 ` [PATCH] intel_ips: quieten "power or thermal limit exceeded" messages Cesar Eduardo Barros
2010-08-26 23:33   ` Joe Perches
2010-08-27  0:11     ` Cesar Eduardo Barros
2010-08-27  0:41       ` Joe Perches
2010-08-27  1:38         ` Cesar Eduardo Barros
2010-08-27  7:39           ` Joe Perches
2010-08-27 23:12             ` Cesar Eduardo Barros
2010-08-28  2:21               ` Joe Perches
2010-08-28 10:46                 ` Cesar Eduardo Barros
     [not found]                   ` <1282994116.1946.226.camel@Joe-Laptop>
2010-08-28 12:52                     ` Cesar Eduardo Barros
2010-08-28 13:01                       ` Cesar Eduardo Barros
2010-08-28 13:29                       ` Joe Perches
2010-08-28 14:18                         ` Cesar Eduardo Barros
2010-08-28 15:23                           ` Henrique de Moraes Holschuh
2010-08-28 19:07                             ` Cesar Eduardo Barros
2010-08-30 16:29                               ` Jesse Barnes
2010-08-30 21:42                                 ` Cesar Eduardo Barros [this message]
2010-09-23 20:31                 ` Jesse Barnes
2010-09-23 20:47                   ` Joe Perches
2010-09-23 20:50                     ` Jesse Barnes
2010-08-27  0:18   ` Alan Cox
2010-08-27  0:22     ` Cesar Eduardo Barros
2010-08-27  1:42   ` Matthew Garrett

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=4C7C25DF.3070401@cesarb.net \
    --to=cesarb@cesarb.net \
    --cc=hmh@hmh.eng.br \
    --cc=jbarnes@virtuousgeek.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=platform-driver-x86@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;
as well as URLs for NNTP newsgroup(s).