From: Matthew Garrett <mjg@redhat.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Cristiano Prisciandaro <cristiano.p@solnet.ch>,
Thomas Renninger <trenn@suse.de>, Dave Jones <davej@redhat.com>,
acpi4asus-user@lists.sourceforge.net,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
Tom Hughes <tom@compton.nu>,
linux acpi <linux-acpi@vger.kernel.org>,
Francesco Lattanzio <f.lattanzio@simail.it>,
Grigori Goronzy <greg@chown.ath.cx>
Subject: Re: [Acpi4asus-user] [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver
Date: Sun, 5 Apr 2009 11:20:57 +0100 [thread overview]
Message-ID: <20090405102057.GA14089@srcf.ucam.org> (raw)
In-Reply-To: <71cd59b00904050043u44d1cd2eu4b8d3aee9027ea17@mail.gmail.com>
On Sun, Apr 05, 2009 at 09:43:40AM +0200, Corentin Chary wrote:
> >> Could it happen that upcoming machines provide this interface (the two ACPI
> >> functions) and also can do real CPU frequency/volt switching, e.g. via
> >> acpi-cpufreq?
> >
> > Probably this interface is a solution specific to machines based on the
> > celeron M: I don't even know if other 'old' models provide the same
> > interface.
>
> Hi,
> We I just received another patch for that (adding a cpufv file in
> sysfs) and I don't really know what to do.
>
> As Grigori Goronzy said, using cpufreq in not a good idea:
I'm not sure I agree. It's clear that ondemand and conservative aren't
sensible choices with the driver, but beyond that...
> > 3) It looks like it is impossible to use more than one cpufreq driver
> > per CPU. This effectively means you can either use the regular ACPI
> > frequency scaling, which switches between multipliers, or SHE. That's
> > unacceptable. SHE is not intended to replace the regular frequency
> > scaling, but to complement it.
I don't think there's a terribly good reason to use the SHE methods if
the CPU supports speedstep. 945 will automatically drop the frontside
bus in the deepest P states. I'd be surprised if it gave any real world
benefits on the atom based systems.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-04-05 10:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 15:27 [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver Cristiano Prisciandaro
2008-11-23 18:04 ` Pavel Machek
2008-12-02 16:15 ` Matthew Garrett
2008-12-02 20:14 ` Pavel Machek
2009-03-16 4:24 ` Len Brown
2009-03-16 8:29 ` Pavel Machek
2009-03-17 8:30 ` Fabio Comolli
2009-03-17 8:59 ` Fabio Comolli
2008-11-24 9:38 ` Tom Hughes
2008-11-24 15:13 ` Thomas Renninger
2008-11-24 16:36 ` Thomas Renninger
2008-11-24 16:41 ` [Acpi4asus-user] " Corentin Chary
2008-11-24 16:48 ` Tom Hughes
2008-11-24 16:58 ` Corentin Chary
2008-11-24 17:07 ` Tom Hughes
2008-11-24 16:46 ` Tom Hughes
2008-11-24 23:02 ` Cristiano Prisciandaro
2009-04-05 7:43 ` [Acpi4asus-user] " Corentin Chary
2009-04-05 7:43 ` Corentin Chary
2009-04-05 10:20 ` Matthew Garrett [this message]
2009-04-05 11:39 ` Grigori Goronzy
2008-11-24 16:39 ` Tom Hughes
2008-11-24 19:09 ` Cristiano Prisciandaro
2008-12-03 19:26 ` Tom Hughes
2008-12-04 1:57 ` Thomas Renninger
2008-12-05 23:05 ` Tom Hughes
2008-12-06 16:35 ` Matthew Garrett
2008-12-07 15:55 ` Tom Hughes
2008-12-09 12:36 ` Pavel Machek
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=20090405102057.GA14089@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=cpufreq@vger.kernel.org \
--cc=cristiano.p@solnet.ch \
--cc=davej@redhat.com \
--cc=f.lattanzio@simail.it \
--cc=greg@chown.ath.cx \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom@compton.nu \
--cc=trenn@suse.de \
/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.