From: Pavel Machek <pavel@suse.cz>
To: Dominik Brodowski <linux@brodo.de>
Cc: Pavel Machek <pavel@suse.cz>,
davej@suse.de, John Clemens <john@deater.net>,
cpufreq@www.linux.org.uk,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Re: cpufreq: allow user to specify voltage
Date: Thu, 6 Mar 2003 21:42:30 +0100 [thread overview]
Message-ID: <20030306204230.GC276@elf.ucw.cz> (raw)
In-Reply-To: <20030228211638.GA888@brodo.de>
Hi!
> And for powernow-k7.c , the file
>
> /sys/devices/sys/cpu0/scaling_setvoltage
>
> should show the current voltage for the current speed (scaling_setspeed).
> "echoing" a different value (must be lower than the current voltage) changes
> the voltage for this frequency only. However, this override is "static" so
> that if you switch to a different frequency in the meantime but get back to
> the one you wanted to override the voltage setting for, the new
> user-specified value is remembered.
>
> This is untested (don't have a powernow-k7-capable notebook), so handle with
> care.
Thanx, it works. I'd drop "can't set higher voltage" limitation
[hardware protects you, anyway, and if you make it so low your system
is unstable you can no longer fix it without reboot], but that's
minor.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
prev parent reply other threads:[~2003-03-06 23:01 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
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 [this message]
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=20030306204230.GC276@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@suse.de \
--cc=john@deater.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox