On Friday 30 March 2007 5:18 pm, Johannes Berg wrote: > On Fri, 2007-03-30 at 17:57 -0600, Jordan Crouse wrote: > About different possible states: I think each of those can have > different possible wakeup sources, ACPI can afaik go to S4 and still be > able to configure the wakeup sources. So I suppose this really needs to > be something like /sys/power/wakeup/<state>/<event> then where <state> > is one of (currently) "mem", "disk" and "standby". Nobody has yet been able to demonstrate user benefit from exposing that level of complexity to userspace. To the contrary, it seems enough to just expose a boolean flag saying whether a given device should try to be a wakeup event source. If the hardware won't allow that in the target system state, so be it; there's no way software can change that. > And then change the > interface of pm_register_wakeup_source to include the state. We don't need such a new interface. - Dave - 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
