From: "Grover, Andrew" <andrew.grover@intel.com>
To: "'Pavel Machek'" <pavel@suse.cz>, Dominik Brodowski <linux@brodo.de>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
hpa@zytor.com, cpufreq@www.linux.org.uk
Subject: RE: cpufreq patches for 2.5.39 follow
Date: Tue, 1 Oct 2002 15:55:38 -0700 [thread overview]
Message-ID: <EDC461A30AC4D511ADE10002A5072CAD0236DEEA@orsmsx119.jf.intel.com> (raw)
> From: Pavel Machek [mailto:pavel@suse.cz]
> How does it interact with ACPI? Ie. I do echo "100%100%foo",
> but ACPI thermal
> managment decides to slow down?
How do you think it should be handled?
Will the ACPI thermal driver be able to use a standard cpufreq interface to
request that the CPU drop to a lower mhz/voltage?
Things get interesting on a system that implements ACPI 2.0-style processor
performance controls, instead of proprietary methods. Then you could have
ACPI thermal telling cpufreq to slow down, which in turn tells the ACPI
processor driver. IMHO this is the way it should work. There is a connection
right now between the ACPI thermal and processor driver, but that is just
there because cpufreq didn't exist. This dependency should be severed, and
cpufreq should go in the middle.
This was discussed on cpufreq a few months ago and I think Dominik even
whipped up some code, but it may have bit-rotted...
> > Support for mobile AMD K7 processors is still in development.
>
> What about mobile celerons?
Mobile Celerons do not support voltage scaling.
Regards -- Andy
next reply other threads:[~2002-10-01 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 22:55 Grover, Andrew [this message]
2002-10-01 22:59 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 23:07 Grover, Andrew
2002-09-28 9:21 Dominik Brodowski
2002-09-30 2:38 ` Pavel Machek
2002-10-02 1:22 ` Alan Cox
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=EDC461A30AC4D511ADE10002A5072CAD0236DEEA@orsmsx119.jf.intel.com \
--to=andrew.grover@intel.com \
--cc=cpufreq@www.linux.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.com \
/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®