On Sun, Apr 17, 2005 at 03:29:17PM -0700, David Brownell wrote: > On Sunday 17 April 2005 1:48 pm, Adam Belay wrote: > > > > So I think each clock could be a power resource. It looks like the > > current code isn't doing much more than turning them on and off. > > They should clk_use()/clk_unuse(), and automatically handle the > activation/deactivation of parent clocks. Some clocks are shared > between multiple devices ... so "on/off" doesn't suffice, those > devices' drivers rely on the clock framework to coordinate. (Or > were you thinking that on/off would match use/unuse? There's no > point to separate enable/disable calls IMO.) Yes, I was thinking power resources could replace use/unuse. So each device could associate a list of required resources by state. Then, when there are not any devices in a state that requires a given resource, the resource could be turned off.
