public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: [PATCH] powernow-k8 max speed sanity check
Date: Fri, 6 Feb 2004 09:28:16 -0800	[thread overview]
Message-ID: <20040206172815.GB8222@atomide.com> (raw)
In-Reply-To: <20040206125623.GC22597@atrey.karlin.mff.cuni.cz>

* Pavel Machek <pavel@ucw.cz> [040206 04:57]:
> 
> > But I meant calculating all the valid values inbetween min and max without
> > relying on getting those values from the BIOS.
> 
> I do not think values can be calculated by some simple
> formula. voltage/frequency relations may be quite complex..
> 
> > I guess the code already does that to figure out how many steps are needed
> > to change between min and max?
> 
> Well, but it steps voltage first, then frequency [going up] or
> frequency first, voltage then [going down]; middle values used by the
> transitions are not too good if you want to be power-efficient.

OK, I see. Then your idea of using a lookup table for blacklisted BIOSes
makes good sense.

Tony

      reply	other threads:[~2004-02-06 17:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31 20:35 [PATCH] powernow-k8 max speed sanity check Tony Lindgren
2004-01-31 23:19 ` Dave Jones
2004-02-03 13:14 ` Pavel Machek
2004-02-05 18:17   ` Tony Lindgren
2004-02-05 18:48     ` Pavel Machek
2004-02-05 19:36       ` Tony Lindgren
2004-02-05 21:33       ` Tony Lindgren
2004-02-05 21:38         ` Pavel Machek
2004-02-05 21:56           ` Tony Lindgren
2004-02-06  0:28             ` Pavel Machek
2004-02-06  1:15               ` Tony Lindgren
2004-02-06 12:56                 ` Pavel Machek
2004-02-06 17:28                   ` Tony Lindgren [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=20040206172815.GB8222@atomide.com \
    --to=tony@atomide.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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