On Tue, May 25, 2010 at 02:25:08PM -0400, Alan Stern wrote: > On Tue, 25 May 2010, Dmitry Torokhov wrote: > > > BTW, If you are concerned about events that already "left" physical > > device but has not reached userspace yet - maybe instead of suspend > > blockers we should make sure that all drivers throughout the chain > > implement suspend/resume and refuse suspending if their queues are not > > empty. In input land that would mean extending suspend routine in > > input_dev and adding one to evdev. > > That's not the only problem. We also have to consider events that have > reached userspace but not yet been fully processed. The user thread > handling the event needs some way to prevent the system from suspending > until it is all done. > It is a problem if kernel initiated suspend transition on its own. I believe that it is userspace responsibility to initiate sustend (and make sure that needs of userspace, including processing of certain events, are served beforehand). -- Dmitry _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
