mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Chris Wedgwood <cw@f00f.org>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	davej@suse.de, linux@brodo.de
Subject: Re: Select voltage manually in cpufreq
Date: Tue, 18 Feb 2003 22:58:19 +0100	[thread overview]
Message-ID: <20030218215819.GC21974@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20030218214726.GB15007@f00f.org>

Hi!

> > I've added possibility to manualy force specified frequency and
> > voltage... That's fairly usefull for testing, and I believe this (or
> > something equivalent) is needed because every 2nd bios seems to be
> > b0rken.
> 
> Why are all the power/cpu patches so complex?  Can't we have a
> two-mode style operation, "slow-low-power" and "fast-high-power" or
> something?  Would that not work with 99% or what people need and also
> be somewhat more uniform across platforms, CPUs, etc?

Well, and does slow-low-power mean 300MHz, 1.4V as bios said, or
300MHz, 1.2V which is probably also safe?

What about
"as-fast-as-possible-but-not-exceed-140MHz-because-batteries-are-
running-low-and-can-not-give-enough-current"? That's different from
"fast-high-power", but it is *also* different from
"slow-low-power". [This actually matters on beasts like zaurus]. What
about
"as-low-power-as-possible-but-make-sure-you-can-keep-display-up"? [On
some machines cpu must be > some HMz for display to still work].

Power managment is complex...
								Pavel
-- 
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.

  reply	other threads:[~2003-02-18 21:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18 21:42 Pavel Machek
2003-02-18 21:47 ` Chris Wedgwood
2003-02-18 21:58   ` Pavel Machek [this message]
2003-02-18 22:08     ` Chris Wedgwood
2003-02-18 22:16       ` Pavel Machek
2003-02-18 22:16       ` Russell King
2003-02-18 22:33         ` Chris Wedgwood
2003-02-19 10:15       ` Dave Jones
2003-02-19 14:43       ` John Bradford
2003-02-18 23:09   ` George Staikos
2003-02-19  2:02   ` Alan Cox
2003-02-19 15:31   ` Pavel Machek

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=20030218215819.GC21974@atrey.karlin.mff.cuni.cz \
    --to=pavel@suse.cz \
    --cc=cw@f00f.org \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.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

all inboxes | Powered by JetHome®