Re: [linux-pm] Re: The evilness of struct usb_device->auto_pm
"Rafael J. Wysocki" <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thursday, 27 September 2007 21:37, Oliver Neukum wrote: > Am Donnerstag 27 September 2007 schrieb Rafael J. Wysocki: > > > But there's a problem, in that the resume methods don't take a message > > > parameter. So they wouldn't know whether they were doing a runtime > > > resume or a system resume. > > > > This is a general problem with the .resume() routines. > > > > If you want to use one for runtime resume, the driver needs to preserve > > information allowing it to figure out what kind of resume is going to happen. > > How? Suppose you > > 1) runtime suspend > 2) whole system suspend > 3) whole system resume > > What kind of resume do you do? System resume, I'd guess. Anyway, if we are going to stop using the freezer during suspend, the locking requirements will probably have to unified between the runtime and system suspend. Greetings, Rafael ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel