From: Francesco Lattanzio <franz.lattanzio@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: FSB scaling for ASUS EeePC 1000H
Date: Tue, 17 Mar 2009 09:26:06 +0100 [thread overview]
Message-ID: <49BF5E9E.8050404@gmail.com> (raw)
In-Reply-To: <20090315190557.GA4324@srcf.ucam.org>
Matthew Garrett ha scritto:
> On Sun, Mar 15, 2009 at 04:01:23PM +0100, Francesco Lattanzio wrote:
>
>> The following patch (against the current "linux-acpi-2.6" source tree)
>> adds the capability of the ASUS EeePC 1000H (and maybe other models as
>> well) to scale the FSB frequency and core voltage. Do not confuse this
>> with cpufreq (SpeedStep and other similar mechanisms): cpufreq changes
>> the internal CPU clock multiplier (and eventually the core voltage too)
>> leaving the FSB frequency untouched.
>>
>
> No, there's no requirement that cpufreq be limited to clock-multiplier
> based methods. It's the right interfae to use for CPU speed control.
>
> (snip patch)
>
> Is this different to the cpufreq driver suggested at
> http://lkml.org/lkml/2008/11/23/115 , other than the latter having
> hardcoded speed values?
>
>
It is exactly the same thing, done differently. Now I ask you, should we
put this feature inside some eeepc-specific cpufreq module, or inside
the eeepc-laptop module? Keep in mind that the 1000H model allows me to
combine the effects of both the cpufreq (through Atom SpeedStep feature)
and these ACPI methods.
--
Francesco Lattanzio <franz.lattanzio@gmail.com>
next prev parent reply other threads:[~2009-03-17 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 15:01 FSB scaling for ASUS EeePC 1000H Francesco Lattanzio
2009-03-15 19:05 ` Matthew Garrett
2009-03-17 8:26 ` Francesco Lattanzio [this message]
2009-03-17 11:34 ` Matthew Garrett
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=49BF5E9E.8050404@gmail.com \
--to=franz.lattanzio@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
/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