[lkml]   [2002]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH][2.5.32] CPU frequency and voltage scaling (0/4)

> > #3 Then the cpufreq driver is called to actually set the CPU frequency.
> >
> > #3 is absolutely ready
> #3 is _not_ ready, if it doesn't include a "policy" part in addition to
> the frequency. That was what I started off talking about: on some CPU's
> you absolutely do _not_ want to set a hard frequency, you want to tell the
> CPU how to behave (possibly together with a frequency _range_).
> Until that is done, no other upper layers can use this low-level
> functionality, since all upper layers would be forced to come up with a
> hard frequency goal.
> THAT is the problem. If you want to build infrastructure for upper layers,
> then that infrastructure has to be able to pass down sufficient
> information from those upper layers.

So... would you take a patch that passed range down to cpufreq "core"?

Dumb cpus would set speed to upper limit while smart cpus would get all
the info...

Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.080 / U:1.488 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site