cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Phil Endecott" <phil_fvnqz_endecott@chezphil.org>
To: cpufreq@lists.linux.org.uk
Subject: How does BIOS "thermal throttling" interact with cpufreq? (on VIA C7)
Date: Thu, 14 Jun 2007 22:26:59 +0100	[thread overview]
Message-ID: <1181856419753@dmwebmail.belize.chezphil.org> (raw)

Dear Cpufreq experts,

I have a Jetway J7F2 motherboard with a VIA C7 processor and have 
recently got CPU frequency scaling working with the ondemand governor.  
It all works very smoothly - thanks.

In the BIOS settup screens there are options for "thermal throttling".  
They allow me to define a threshold voltage and a "duty cycle"; the 
screens are rather vague and there's nothing about it in the board 
documentation.  My guess is that when the CPU temperature reaches this 
threshold the clock speed is reduced.  I have looked at the datasheet 
for the chip that includes the temperature monitoring logic, and asked 
about it on the lm-sensors (aka hwmon) mailing list, and there seems to 
be an "over temp" output signal from this chip.  (The is also an 
"alarm" output, with a separate threshold register, which I think goes 
to the speaker.)

Does anyone know how this stuff works, and how it interacts with 
cpufreq?  Could it be that the "over temperature" signal is actually 
just an interrupt and software is supposed to respond by changing the 
frequency?  Does cpufreq need to be aware of this throttling function 
(i.e. having enabled cpufreq, have I unintentionally disabled this 
thermal protection?)

Any thoughts would be much appreciated.

Regards,

Phil.

             reply	other threads:[~2007-06-14 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14 21:26 Phil Endecott [this message]
2007-06-15 16:31 ` How does BIOS "thermal throttling" interact with cpufreq? (on VIA C7) Wes Felter

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=1181856419753@dmwebmail.belize.chezphil.org \
    --to=phil_fvnqz_endecott@chezphil.org \
    --cc=cpufreq@lists.linux.org.uk \
    /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