On Tue, 25 Jul 2006, David Brownell wrote: > > Hmm ... I just noticed that the swsusp code path (PM_SUSPEND_DISK) > is ignoring the new suspend_prepare() mechanism. > > That doesn't seem like a good thing ... Linus, is there a reason you > did it that way? Just because I found that neither interesting nor testable in my environment. > Why is there no sibling resume_complete()? ISTR > that Ben was the advocate of a suspend_prepare(), but the use cases > for this call are unclear to me ... Havign a resume_complete() would be nice for a number of things, like reloading firmware etc (which usually requires not just the device being back and fully working, but more importantly, requires user space to be alive again). Linus
