On Wed, Aug 28, 2002 at 09:25:53PM +0100, Alan Cox wrote:
> On Wed, 2002-08-28 at 20:49, Linus Torvalds wrote:
> That argument ultimately boils down to "should the /proc interface to
> cpufreq" be a seperate module to the core cpu_freq code called by kernel
> policy engines like ACPI. The answer is obviously "yes" - /proc is just
> one of the policy engines.
So, what do all of you think of the following implementation?
#1 The "policy modules" (/proc-interface, kernel-based frequency selector,
...) determine the target CPU frequency.
#2 This is then passed to the cpufreq core. There it is validated,
loops_per_jiffy and other values are adjusted.
#3 Then the cpufreq driver is called to actually set the CPU frequency.
#3 is absolutely ready, #2 in parts (the "policy module" interface is
missing, and the /proc-interface needs to be removed), and #1 is TBD.
Comments?
Dominik
-
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 : Sat Aug 31 2002 - 22:00:24 EST