public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Joe Harvell <jharvell+lists.linux-kernel@dogpad.net>
Cc: linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: Re: ACPI C and P states on Conroe
Date: Tue, 30 Jan 2007 20:17:47 -0500	[thread overview]
Message-ID: <200701302017.47599.lenb@kernel.org> (raw)
In-Reply-To: <45BF81CF.2060801@dogpad.net>

On Tuesday 30 January 2007 12:35, Joe Harvell wrote:
> I am trying to enable all the power saving features I can on my Conroe
> E6600.  After much searching on the web, I am a little confused about
> the Linux kernel support for ACPI on the Conroe.
> 
> Here is my setup:
> Intel Core2 Duo E6600
> Asus P5-B Deluxe board (Intel P965).
> I am running a Gentoo kernel based on 2.6.19.4.
> 
> I have managed to enable EIST using cpufreq with the speedstep-centrino
> driver.  But my understanding from browsing the ACPI spec is that this
> is still within C0, i.e. not much power savings.

Right, P-states are effective only when code is executing,
and on this processor (with C1E) will have no effect on idle power.

> Here are my questions:
> 
> 1) For P states, which cpufreq driver should I be using?  I've heard
> speedstep-centrino is deprecated (but only some aspects of it) that are
> being moved into acpi-cpufreq.  But I can't get acpi-cpufreq to load in
> my kernel version.

In 2.6.19 I believe that speedstep-centrino is the one to use.
The transition to acpi-cpufreq happens in 2.6.20.

> Also, I would have thought speedstep-ich would be 
> the driver, just based on the name.

Don't use speedstep-ich.

> How do I know (other than trying 
> all modules to see which one loads) which one I should be using?
> 2) What kind of support for C1-C3 does the Conroe have?  The ACPI spec
> says C2 and C3 require chipset support on the motherboard.  Does P965
> have that.  Does it matter between boards (e.g. P5B)?

I believe that Conroe currently supports just C1 --
this is true for the ones I have.

Internally it is an "Enhanced C1" called C1E where the voltage is reduced
in C1-- but this is transparent to software, which thinks it is just C1.

You can observe this in
/proc/acpi/processor/*/power

> 3) What versions of the kernel support C1-C3 states?  What kernel
> options are germane to this?  What libraries/tools are involved?

C1-C3 have been supported for a long time.
2.6.20 adds a few tweaks to use a more efficient implementation,
but you'll not notice a difference on today's desktop processor.

cheers,
-Len

  reply	other threads:[~2007-01-31  1:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 17:35 ACPI C and P states on Conroe Joe Harvell
2007-01-31  1:17 ` Len Brown [this message]
     [not found] <fa.kcyyw0/u0jusCdUVaHf0ecFyj0E@ifi.uio.no>
2007-01-30 23:09 ` Robert Hancock
2007-01-31  0:18   ` Joe Harvell
  -- strict thread matches above, loose matches on Subject: below --
2007-01-30 17:33 Joe Harvell
2007-01-30 22:31 ` Pallipadi, Venkatesh

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=200701302017.47599.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=jharvell+lists.linux-kernel@dogpad.net \
    --cc=linux-kernel@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