On Tue, 25 Feb 2003, Pavel Machek wrote:
> Hi!
>
> > > 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
>
> Okay, I see.
>
> > > > - 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.
>
> So I guess adding /sys/bus/system/devices/cpu0/voltage? Should code to
> do that be in kernel/cpufreq.c or is it possible to do sysfs from
> powernow-k7 [it does not seem easy]?
Pavel
I agree, there shoul dbe a way to add sysfs files from a cpufreq driver
module. I told dave I was looking into overriding the powernow tables,
but I can't seem to get enough time away from my day job right now.
for the powernow driver, and the userspace governor, I'd like to export a
file "current_setting" or something that contains:
<frequency> <voltage> <fsb? maybe for other drivers>
A write to this file of one, two, or three values would result in changing
the frequency to the closest standard table match we have. Unless, the
user specifies an "override" flag as a module parameter. If the override
flag is set, then writing to that file will set the speed and voltage to
exactly what you specify (within the min/max hardware limits), and
basically ignore the standard BIOS table.
simple, elegant, gives standard default behavior....but allows one to
override the tables if they -swear- they know better. But it's really
tough to do without a way to add sysfs files from the driver itself.
john.c
--
John Clemens http://www.deater.net/john
john@deater.net ICQ: 7175925, IM: PianoManO8
"I Hate Quotes" -- Samuel L. Clemens
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 28 2003 - 22:00:30 EST