All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Frank <mflt1@micrologica.com.hk>
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: Luigi Belli <lbelli@crema.unimi.it>, cpufreq@www.linux.org.uk
Subject: Re: Cpufreq: powernow-k7 weirdness
Date: Mon, 7 Jul 2003 23:06:10 +0800	[thread overview]
Message-ID: <200307072306.13290.mflt1@micrologica.com.hk> (raw)
In-Reply-To: <20030707131252.GC7796@poupinou.org>

On Monday 07 July 2003 21:12, Ducrot Bruno wrote:
> > The actual minimum time between steps depends on systems design and can
> > only be established by watching the (core) voltage on an oscilloscope
> > while modulating cpufreq/ACPI settings. The time used should be double
> > or triple the minimum for longterm stability. It would be better if
> > Mainboard manufacturers would specify this minimum time.
>
> That is suposed to be done via a BIOS table (with signature
> AMDK7PNOW!) for the powernow-k7 driver, but is used for the
> CPU only (I believe), and I guess that anyway this occur
> only when a valid core voltage is applied to the CPU (well,
> I hope).
> But perhaps this table do not give appropriate values on some system?
>
> Actually, I was wondering why the _PSS method (from ACPI) give
> a settling time of 125us, instead of 100us for some systems.

100us vs 125us won't matter unless the margin is too small already.

I don't know anything about the big CPU chip requirements as I have 
never read a datasheet  on on those big beasts.

My comments were related to the (analog side of the) power supply
limitations. 

IMHO mainboard Vcore switchers could do a step in 100us or so, or full scale 
over 10 steps or so, (weaker) main power supplies would likely have trouble 
as their switching frequency is much lower. Perhaps a mainboard designer
could comment?

Regards
Michael


-- 
Powered by linux-2.5.74-mm1. Compiled with gcc-2.95-3 - mature and rock solid

My current linux related activities:
- 2.5 yenta_socket testing
- Test development and testing of swsusp and ACPI S3
- Everyday usage of 2.5 kernel

More info on 2.5 kernel: http://www.codemonkey.org.uk/post-halloween-2.5.txt

  reply	other threads:[~2003-07-07 15:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-06  1:00 Cpufreq: powernow-k7 weirdness Juliusz Chroboczek
2003-07-06  1:21 ` Ducrot Bruno
2003-07-06 17:11   ` Carl Thompson
2003-07-06 17:28     ` Jay Goodman Tamboli
2003-07-06 17:43       ` Carl Thompson
2003-07-06 18:48         ` Ducrot Bruno
2003-07-06 21:56           ` Luigi Belli
2003-07-07  4:16             ` Michael Frank
2003-07-07 13:12               ` Ducrot Bruno
2003-07-07 15:06                 ` Michael Frank [this message]
2003-07-07 16:32                   ` Daniel Thor Kristjansson
2003-07-07 12:58   ` Juliusz Chroboczek
2003-07-07 13:32     ` Ducrot Bruno
2003-07-07 17:32       ` Dave Jones

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=200307072306.13290.mflt1@micrologica.com.hk \
    --to=mflt1@micrologica.com.hk \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ducrot@poupinou.org \
    --cc=lbelli@crema.unimi.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.