public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Matthew Garrett <mjg@redhat.com>
Cc: Luca Tettamanti <kronos.it@gmail.com>,
	Thomas Renninger <trenn@suse.de>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hans de Goede <hdegoede@redhat.com>,
	khali@linux-fr.org
Subject: polling (Re: [PATCH] ACPI: add "auto" to acpi_enforce_resources)
Date: Thu, 02 Apr 2009 18:45:59 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0904021828110.9182@localhost.localdomain> (raw)
In-Reply-To: <20090204060513.GA28321@srcf.ucam.org>


On Wed, 4 Feb 2009, Matthew Garrett wrote:

> On Wed, Feb 04, 2009 at 12:52:06AM -0500, Len Brown wrote:
> 
> > While it is slightly off-topic of the (I agree, real)
> > technical issue here, note that polling is not "normal" on ACPI systems.
> > [1] was on  SuSE Linux 10.0, which on their own decided to
> > over-ride the kernel and enable thermal zone polling by default.
> 
> Checking the DSDTs I have to hand, it seems that polling is expected on 
> about 5% of systems via an explicit _TZP and on almost all machines via 
> _TSP. Even on systems where thermal notifications are provided, it's 
> still up to the OS to poll the zone to find the current temperature and 
> take appropriate action. There's still a window for native smbus drivers 
> to screw everything up.

FWIW

In the last 6 years, I've seen exactly 3 systems with a non-zero _TZP.
An old Averatec laptop asked for 1 second, and two recent EEE-PC's ask for 
30 seconds.  Dunno why Asus has made this leap backwards.

_TSP is a different beast.  It only exists in the context of _PSV and 
_PSL.

-Len

ps. I just noticed something in the spec under _PSL...
"If a linear performance control register is not defined(..) for a 
processor defined in _PSL or for a processor device in the zone as 
indicated
by _TZM, then the processor must support processor performance states
(in other words, the processor's processor object must include _PCT, _PSS, 
and _PPC).

Interesting, here is an official tie in of P-states and passive trip 
points that I'd not noticed before....



      parent reply	other threads:[~2009-04-02 22:46 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25 21:05 [PATCH] ACPI: add "auto" to acpi_enforce_resources Luca Tettamanti
2009-01-26  8:37 ` Hans de Goede
2009-01-29 10:30 ` Thomas Renninger
2009-01-29 15:16   ` Luca Tettamanti
2009-01-29 16:29     ` Thomas Renninger
2009-01-29 18:58       ` Hans de Goede
2009-01-29 21:31         ` Jean Delvare
2009-01-30 14:29         ` Thomas Renninger
2009-02-01 21:22           ` Luca Tettamanti
2009-02-02  9:11             ` Jean Delvare
2009-02-02 11:38               ` Luca Tettamanti
2009-02-02 17:22                 ` [PATCH 1/2] RFC: ACPI: Interface for ACPI drivers to place quirk code which gets executed early Thomas Renninger
2009-02-02 20:22                   ` Luca Tettamanti
2009-02-03 13:08                     ` Thomas Renninger
2009-02-03 13:45                       ` Luca Tettamanti
2009-02-03 14:19                         ` Jean Delvare
2009-02-04 13:37                     ` Thomas Renninger
2009-02-02 17:22                 ` [PATCH 2/2] RFC: ACPI: Set enforce_resources to strict if a ATK0110 device is found in namespace Thomas Renninger
2009-02-02 20:29                   ` Luca Tettamanti
2009-02-02 11:38             ` [PATCH] ACPI: add "auto" to acpi_enforce_resources Thomas Renninger
2009-01-29 21:15       ` Luca Tettamanti
2009-02-04  5:52     ` Len Brown
2009-02-04  6:05       ` Matthew Garrett
2009-02-04  8:37         ` Hans de Goede
2009-02-04 13:17           ` Matthew Garrett
2009-02-04 13:26             ` Jean Delvare
2009-02-04 14:20               ` Matthew Garrett
2009-02-10 13:57                 ` Jean Delvare
2009-02-10 14:08                   ` Matthew Garrett
2009-02-10 15:32                     ` Hans de Goede
2009-02-10 16:24                       ` Jean Delvare
2009-02-27 13:27                         ` Pavel Machek
2009-03-24 12:39                           ` Luca Tettamanti
2009-03-24 13:21                             ` Hans de Goede
2009-03-24 13:43                               ` Jean Delvare
2009-03-24 14:29                                 ` Hans de Goede
2009-03-29 20:16                               ` Luca Tettamanti
2009-03-29 20:33                                 ` Pavel Machek
2009-03-29 20:55                                 ` Jean Delvare
2009-03-29 22:01                                   ` Luca Tettamanti
2009-03-30  7:36                                     ` Jean Delvare
2009-04-02 22:59                                     ` Len Brown
2009-04-03  9:40                                       ` Jean Delvare
2009-02-12 12:44                     ` Jean Delvare
2009-04-02 22:45         ` Len Brown [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=alpine.LFD.2.00.0904021828110.9182@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=khali@linux-fr.org \
    --cc=kronos.it@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --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