On Wednesday 23 March 2005 11:46 am, David Brownell wrote: > Thing is, it's the system power states that are placing clock > constraints on devices. On OMAP, going into "deep sleep" means > you've got to stop using the 48 MHz clock. For "big sleep", > you can keep using that clock. Most other CPUs have similar > constraints: multiple system states, defined primarily by > clock usage. So to focus on one point: "pm_message_t" doesn't work well at all, since it doesn't have a way to identify the target system power state, and drivers thus have no way to see if they should drop their requests for those clocks or whether the hardware should keep working away. - Dave
