Hi! > >> If you ignore wakelocks with timeouts, the current > >> wakelock interface can be implemented with a global atomic_t to > >> prevent suspend, and a per wakelock atomic_t to prevent a single > >> client from changing the global reference count by more than one. > >> > >> There are a couple of reasons that I have not done this. It removes > >> the ability to easily inspect the system when it is not suspending. > > > > Care to elaborate? > > If you have a single atomic_t and it is not 0, you do not know who > incremented it. Which is okay for already debugged system. For debugging, yes some support can be nice. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
