On Fri, Jun 23, 2006 at 09:26:26AM -0700, David Brownell wrote: > On Thursday 22 June 2006 4:31 pm, Benjamin Herrenschmidt wrote: > > - cpufreq (this is a design bug with cpufreq with the "core/midlayer" > > trying to get in charge instead of the driers and registering a sysdev > > which is very wrong). > > That could stand some elaboration in a separate thread; there are folk > working to enhance cpufreq so that it handles other frequency/voltage > scaling approaches. I happened to notice that cpufreq isn't even using > the driver model very well, too ... On a related note, let's remember that cpufreq needs a sort of "FREEZE" functionality, on some platforms, before transitioning the cpu operating point. Moreover, we need similar stuff for PCI resource rebalancing (although this case would be partial tree suspending), a feature that will likely become very necessary in the near future. It would be nice if the suspend model was robust enough to handle these runtime device suspend cases as well. Thanks, Adam
