From: Dominik Brodowski <linux@brodo.de>
To: Pavel Machek <pavel@suse.cz>
Cc: cpufreq@www.linux.org.uk, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: cpufreq: allow user to specify voltage
Date: Tue, 25 Feb 2003 19:24:14 +0100 [thread overview]
Message-ID: <20030225182414.GA3242@brodo.de> (raw)
In-Reply-To: <20030225180311.GI12028@atrey.karlin.mff.cuni.cz>
Hi!
On Tue, Feb 25, 2003 at 07:03:11PM +0100, Pavel Machek wrote:
> Hi!
>
> Well, look again; if you use mVforce, it forces *just one* frequency
> (min=max=freq you specified), so it is actually okay.
But min=max=freq is awful... I know, I reccommended it sometimes, but with
the appearance of the userspace governor (already available on the cpufreq
homepage, http://www.brodo.de/cpufreq/advanced.html , will be submitted
soon) min=max=freq is deprecated.
> But I agree that hacking proc_intf is not the right thing to do. I did
> not see that sysfs access. Where is it?
kernel/cpufreq.c
> > - selecting the voltage manually is something which is only valid for some
> > very few drivers - so let's only export one sysfs file[*] for these
> > drivers.
>
> Very few drivers? It should be common for at least Intel and AMD, no?
No. Intel doesn't let you select the exact voltage. IIRC, only vew
VIA/Cyrix-longhaul-capable processors and, of course, powernow-k7 are vaild
targets for such a patch.
Dominik
next prev parent reply other threads:[~2003-02-25 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 22:55 cpufreq: allow user to specify voltage Pavel Machek
2003-02-25 0:41 ` Dominik Brodowski
2003-02-25 18:03 ` Pavel Machek
2003-02-25 18:24 ` Dominik Brodowski [this message]
2003-02-25 19:09 ` Pavel Machek
2003-02-25 19:28 ` John Clemens
2003-02-25 19:33 ` Pavel Machek
2003-02-28 21:16 ` [PATCH][RFC] " Dominik Brodowski
2003-03-06 0:29 ` Pavel Machek
2003-03-06 0:36 ` Pavel Machek
2003-03-06 20:42 ` 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=20030225182414.GA3242@brodo.de \
--to=linux@brodo.de \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.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 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.