From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: acpi-devel@lists.sourceforge.net, cpufreq@www.linux.org.uk
Subject: Re: [ACPI] [PATCH 1/2] 2.6: use scaling_available_freqs in acpi-cpufreq-ioport driver
Date: Tue, 24 Feb 2004 15:43:18 +0100 [thread overview]
Message-ID: <20040224144318.GA9702@dominikbrodowski.de> (raw)
In-Reply-To: <20040224125628.GA438@elf.ucw.cz>
[-- Attachment #1.1: Type: text/plain, Size: 469 bytes --]
On Tue, Feb 24, 2004 at 01:56:28PM +0100, Pavel Machek wrote:
> Hi!
>
> > Export an array of supported frequencies in sysfs
> > [scaling_available_frequencies]
>
> Would it be possible to export [frequency/voltage] pairs, and allow
> user to change it?
IMO, NO! While this might be a necessity for powernow-k7, the generic acpi-io
driver should stay clean of such overrides et al. If you need to modify the
ACPI tables, there are other ways.
Dominik
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq
next prev parent reply other threads:[~2004-02-24 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 8:31 [PATCH 1/2] 2.6: use scaling_available_freqs in acpi-cpufreq-ioport driver Dominik Brodowski
2004-02-24 12:56 ` [ACPI] " Pavel Machek
2004-02-24 14:43 ` Dominik Brodowski [this message]
2004-02-25 10:26 ` Pavel Machek
2004-02-24 21:00 ` Tomasz Ciolek
2004-02-24 22:16 ` Pavel Machek
2004-02-26 17:28 ` Bruno Ducrot
2004-02-26 21:50 ` Pavel Machek
2004-03-01 17:54 ` Bruno Ducrot
2004-03-01 18:03 ` Pavel Machek
[not found] ` <20040301180325.GA562-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-03-03 16:22 ` Bruno Ducrot
2004-03-12 14:52 ` [ACPI] " Dominik Brodowski
2004-03-12 20:01 ` 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=20040224144318.GA9702@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=acpi-devel@lists.sourceforge.net \
--cc=cpufreq@www.linux.org.uk \
--cc=pavel@ucw.cz \
/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