public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Slagter <erik@slagter.name>
To: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] amd76x_pm: C3 powersaving for AMD K7
Date: Fri, 03 Feb 2006 10:39:32 +0100	[thread overview]
Message-ID: <1138959572.18273.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20060203093335.GA4403@tangens.sinus.cz>

[-- Attachment #1: Type: text/plain, Size: 933 bytes --]

On Fri, 2006-02-03 at 10:33 +0100, Pavel Troller wrote:

> > Isn't there any other way to tell the operating system that the C2/C3
> > states are unusable (e.g. by simply telling they're not there?). This
> > looks so obfuscated...
> 
>   The problem is that the table (RSDT) has a fixed format and the values have
> reserved positions. Putting 0 there would mean zero (unmeasureble) latency,
> which would be the best case, of course. So to disable the feature, "out of
> range" method was selected. Yes, it would be nice to have some "special" value
> there, like FFFF, but it is not a common practice.

Still I don't get it. Current linux acpi implementation suggests there
are 8 C states. My laptop says the processor supports 4 C states, my
other laptop says it has 3 C states. Do you mean the table always has 8
C entries, and all of the unusable states are marked "unusable"? In that
case I would understand.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2771 bytes --]

  reply	other threads:[~2006-02-03  9:39 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  1:35 [PATCH] amd76x_pm: C3 powersaving for AMD K7 Brown, Len
2006-02-02  1:50 ` Alan Cox
2006-02-02  9:50   ` Erik Slagter
2006-02-02 19:38     ` Tony Lindgren
2006-02-03  9:21 ` Erik Slagter
2006-02-03  9:33   ` Pavel Troller
2006-02-03  9:39     ` Erik Slagter [this message]
2006-02-03 10:14       ` Pavel Troller
2006-02-03 10:28         ` Erik Slagter
  -- strict thread matches above, loose matches on Subject: below --
2006-02-03 18:40 Brown, Len
2006-02-04 10:31 ` Erik Slagter
2006-02-04 10:49   ` Pavel Troller
2006-02-03 18:28 Brown, Len
2006-02-03 18:20 Brown, Len
2006-02-03  8:45 Brown, Len
2006-02-03  9:35 ` Erik Slagter
2006-02-03 10:31   ` Pavel Troller
2006-02-03 14:16 ` Joerg Sommrey
2006-02-03 15:59 ` Juhani Rautiainen
2006-02-03 17:02   ` Erik Slagter
2006-02-08 20:10   ` Pavel Machek
2006-02-02 22:24 Joerg Sommrey
2006-02-02 22:37 ` Andrew Morton
2006-02-03  7:03   ` Joerg Sommrey
2006-02-02 22:43 ` Dave Jones
2006-02-01 18:11 Brown, Len
2006-02-01 18:18 ` Erik Slagter
2006-02-01 18:40   ` Tony Lindgren
2006-02-01 19:13 ` Joerg Sommrey
2006-01-31 18:55 Joerg Sommrey
2006-02-01  3:34 ` Andrew Morton
2006-02-01 10:25   ` Erik Slagter
2006-02-01 17:20   ` Tony Lindgren

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=1138959572.18273.18.camel@localhost.localdomain \
    --to=erik@slagter.name \
    --cc=linux-acpi@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