> You are, of course, correct. Ultimately the only requirement we have > is that there exists a way for userspace to determine if the system > woke up because of a user-triggered event. The actual mechanism by
No. That is irrelevant. You need a way to ascertain if a user triggered event has occurred since you suspended. The two are not the same thing. If your box wakes up due to something like a wireless card deciding it needs to poke the base station and the user hits a key a microsecond after wakeup then you want the display on. The question is never "did the user wake the machine" the question is "did the user do something that takes me out of 'lucid sleep/snooze/whatever' since I suspended". Every user event could equally occur a microsecond after a wakeup from a non user source, so every time you must ask the "since suspend" question. In fact if you had some kind of hypoethetical event counter incremented by the device on it causing a wakeup event *or* an event while active (and no way to tell them apat) that would provide a correct race free interface to figure out if the display ought to be on It doesn't solve the powering off as a key is hit race but that's a different beast. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
