On Sun, 2007-07-08 at 19:44 -0700, David Brownell wrote: > On Sunday 08 July 2007, Marcelo Tosatti wrote: > > On Sun, Jul 08, 2007 at 01:15:40PM -0700, David Brownell wrote: > > > On Sunday 08 July 2007, Richard Hughes wrote: > > > > > > That is, we may want to provide a bit more information about the > > > specific event which triggered wakeup. I don't believe there is > > > such an interface, in general. > > > > What would be a nice interface? Perhaps an additional file under > > /sys/devices/.../power/wakeup_fired or something (only for devices with > > can_wakeup set). > > Better a /sys/power/wakeup_event (or whatever) that's more easily > found. It could link to the device issuing the event. Good plan. > > > Plus, the notion seems kind of racey to me. (If you press a key > > > right while the wakealarm fires, you don't want hibernation..) > > > > Then you check if the any key or other wakeup event has happened other > > than RTC... I don't see any problem with that. > > It might be best not to need to re-activate the whole system from > STR though ... it ought to be possible to just power off, having > already written the image to disk. Right? > > Yes, there's all that stuff about how to quiesce the system properly, > freezer/icebox/flamesuits/etc. Regardless, going from STR to fully > operational and then hibernating would take time and energy that > might not be available... Sure, although quick-suspend on a few minutes idle, slow hibernate-on-long idle is one of the biggest requested features of g-p-m. Richard. - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
