cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot@poupinou.org>
To: Wouter Verhelst <wouter@grep.be>
Cc: cpufreq@www.linux.org.uk
Subject: Re: p4-clockmod doesn't seem to allow the highest possible speed
Date: Mon, 12 Jan 2004 13:26:13 +0100	[thread overview]
Message-ID: <20040112122613.GE14031@poupinou.org> (raw)
In-Reply-To: <20040111195619.GA25048@grep.be>

On Sun, Jan 11, 2004 at 08:56:19PM +0100, Wouter Verhelst wrote:
> On Sun, Jan 11, 2004 at 06:35:47PM +0100, Dominik Brodowski wrote:
> > On Sat, Jan 10, 2004 at 08:35:26PM +0100, Wouter Verhelst wrote:
> > > That happens both when it's in P0 or P1.
> > 
> > So ACPI works to set the processor in P0 and P1?
> 
> Yes.
> 
> > If so, you really really should use the ACPI cpufreq driver instead of
> > the p4-clockmod driver. The former will offer you true "SpeedStep"
> > support, the latter only some clock modulation which won't save you
> > much energy as ACPI supports the C2 idle state anyway. 
> 
> Ah, so what p4-clockmod does is not SpeedStep?
> 
> Hm. That sucks.

No.  p4-clockmod is not SpeedStep.  Normal.  As Dominik say, p4-clockmod
is *not* intended for power comsuption issues.

There is normally two reasons for slowing a CPU:

1- change voltage of processor (SpeedStep, Powernow, etc.)
   The usage for is to get more battery life, or to get less power comsuption
   for the system.

2- throttling the CPU via clock modulation (P4 only), or by generating
   a signal which toggle the STP# pin of a CPU.  The usage for it is
   to cool the CPU instead of turning on/off the CPU fan.  It is also
   used if the fan is not sufficiant to cool enough the CPU.

1 and 2 do not have the same goal.  The CPUFreq project currently only
handle case 1- (via policy, governor, etc.).  But I'm thinking about
designing case 2- for the cpufreq core (there is already something for,
but it is not exactly what I would expect), and that should rely on
lm-sensors or/and ACPI thermal.

Cheers,

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

      parent reply	other threads:[~2004-01-12 12:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 18:18 p4-clockmod doesn't seem to allow the highest possible speed Wouter Verhelst
2004-01-10 10:15 ` Dominik Brodowski
2004-01-10 11:08   ` Wouter Verhelst
2004-01-10 13:18     ` Dominik Brodowski
2004-01-10 15:02       ` Wouter Verhelst
2004-01-10 15:38         ` Dominik Brodowski
2004-01-10 16:30           ` Wouter Verhelst
2004-01-10 15:21       ` Wouter Verhelst
2004-01-10 15:41         ` Dominik Brodowski
2004-01-10 16:32           ` Wouter Verhelst
2004-01-10 18:53             ` Ducrot Bruno
2004-01-10 19:35               ` Wouter Verhelst
2004-01-11 15:48                 ` Ducrot Bruno
2004-01-11 17:30                   ` Dominik Brodowski
2004-01-11 18:05                     ` Ducrot Bruno
2004-01-11 17:35                 ` Dominik Brodowski
2004-01-11 19:56                   ` Wouter Verhelst
2004-01-11 20:06                     ` Dominik Brodowski
2004-01-11 20:24                       ` Wouter Verhelst
2004-01-12 12:26                     ` Ducrot Bruno [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=20040112122613.GE14031@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=wouter@grep.be \
    /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