On Sat, 2005-03-12 at 11:29 +1100, Benjamin Herrenschmidt wrote: > On Fri, 2005-03-11 at 17:08 -0700, Jordan Crouse wrote: > > On Sat, 12 Mar 2005 10:54:55 +1100 > > "Benjamin Herrenschmidt" <benh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > On that note, no matter where we have it, I'd like to limit it to > > > > 6-8 people, with at most maybe 10. I don't wish to exclude anyone, > > > > but I think that smaller groups can remain more focused. Plus, > > > > there's all those sociological studies that say 6-7 people is the > > > > optimal size for a discussion group. :) > > > > > > Us, Nigel, David Brownell, Alan, Pavel, Brown, we are already 7... ? > > > > Are there any logical divisions of area of interest that could result in > > multiple productive meetings? > > Not sure. There are 2 different "main" areas, which are the global > system suspend/resume, and the "local" or "dynamic" power management of > devices & busses. We have a good solution for the first, but not for the > second at this point, so I would expect that we concentrate on that > part. > > Plus some always-pending issues for global suspend, the biggest one > beeing video chips that need a re-POST on wakeup. > > Ben. Under the topic of dynamic power management, there are a few logical divisions of interest: 1.) Low-level - providing the bus support and facilities for higher level power management (ex. the current work I'm doing with the PCI bus driver). Also support for power domains might fall under this category. 2.) Driver state and driver relationships - logical vs. physical, driver API, threading power management to transition multiple devices at once, etc 3.) Power Management Policy - determining which behavior to take for various classes of devices, how to determine idleness etc., and how to control/monitor those devices. 4.) Userspace - how to notify of power changes, how to allow the user to control power management. Anything else? Thanks, Adam
