On Fri, 28 May 2010 15:35:16 +0200 Pavel Machek <pavel@xxxxxx> wrote: > Hi! > > > > I don't fully understand your requirements for accounting of devices drivers > > > rejecting or blocking a suspend, so I cannot say precisely how that would fit > > > in. Maybe you just need to know - whenever the 'suspend request' completes - > > > what the wakeup events were. It shouldn't be too hard to export that to > > > user-space via sysfs. > > > > > > I won't propose an exact enhancement to the user-space interface for > > > requesting a suspend, but I suspect it should expose each of > > > suspend_prepare > > > suspend_devices_and_enter > > > suspend_finish > > > (or close analogues there-of) to user-space. It is tempting to map those to > > > "open-for-write", "write", "close", but I'm not sure that suspend_prepare > > > would be appropriate if the app was about to write "disk" - it is a pity that > > > both suspend and hibernate use the same sysfs file. > > > > > > So just fix the bug, and everyone will be happy :-) > > > > > > > I already have, but everyone do not appear to be happy. > > Half of the code you submitted was infrastructure for debugging > userspace. Sorry, that does not count as a bugfix. > That is not the issue here. _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
