From: Thomas Renninger <trenn@suse.de>
To: Tom Hughes <tom@compton.nu>
Cc: Cristiano Prisciandaro <cristiano.p@solnet.ch>,
Dave Jones <davej@redhat.com>,
cpufreq@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver
Date: Mon, 24 Nov 2008 16:13:24 +0100 [thread overview]
Message-ID: <200811241613.25557.trenn@suse.de> (raw)
In-Reply-To: <492A7632.4040106@compton.nu>
On Monday 24 November 2008 10:38:58 am Tom Hughes wrote:
> Cristiano Prisciandaro wrote:
> > From: Cristiano Prisciandaro <cristiano.p@solnet.ch>
> >
> > The bios of the eeepc 900 exposes an acpi method that allows clocking
> > the cpu to 630/900 MHz. This driver allows controlling the frequency
> > switch through the cpufreq subsystem.
>
> I should perhaps add at this point that I have an alternative patch
> based on Cristiano's code, which adds this cpufreq driver to the
> existing eeepc-laptop module rather than creating a separate module for it.
>
> Personally I'm quite happy with either solution so I'll leave it to you
> to decide what is the best way to go, but my patch is available if you
> want it.
Either way, shouldn't you be able to provide a dmi matching module alias:
MODULE_ALIAS("dmi:...")
for autoloading?
Or are these two cpufreq functions part of an ACPI device you could match for,
then it should get an ACPI driver?
If this ACPI device provides more functions, then these should probably also
be added to this driver.
Splitting the OS drivers the same way as BIOS splits up functionality into
ACPI devices is a good idea.
Could you paste at least the whole ACPI device in which:
#define ASUS_CPUFV_READ_METHOD "CFVG"
#define ASUS_CPUFV_WRITE_METHOD "CFVS"
sit or better point to an acpidump/dsdt output.
Thomas
next prev parent reply other threads:[~2008-11-24 15:13 UTC|newest]
Thread overview: 28+ 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 [this message]
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 10:20 ` Matthew Garrett
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=200811241613.25557.trenn@suse.de \
--to=trenn@suse.de \
--cc=cpufreq@vger.kernel.org \
--cc=cristiano.p@solnet.ch \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom@compton.nu \
/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