Hi! > > That need not happen at once (eg. in one patch or something). Once we've > > introduced the basics, the changes can be made gradually wherever necessary, > > step by step. > > If you are OK with merging an unfinished system then this may work. Good. > > So, I'd suggest to just separate the timeouted suspend blockers from the > > basic code and introduce the latter first. > > How do you want to handle drivers that return -EBUSY from suspend. The > basic code uses a wakelock with a timeout to handle this now. Without > this we can either try suspend again immediately, or activate a > suspend blocker and use a timer to release it. Just printk() and complain. That should be good enough solution for now... (Those drivers are arguably buggy already. If user told machine to go to sleep, it should not randomly refuse to do that.) 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
