On Thu, 2009-02-26 at 12:34 -0800, Arve Hjønnevåg wrote:> That is enough for drivers that use wakelocks to abort suspend (if I> fix the wakelock code to not use a platform device as its last abort> point). It is not enough if you don't have wakelocks, since the> interrupt can occur after suspend_late has been called and the driver> has no way to abort suspend.> I still don't quite see how you deal with the race anyway. Ie. Evenwithout Rafael patch, what if the interrupt occurs after your sysdevsuspend ? In general, unless they are level sensitive, wakeup interrupts tend toalways be somewhat racy. Cheers,Ben. _______________________________________________linux-pm mailing listlinux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx://lists.linux-foundation.org/mailman/listinfo/linux-pm
