On Thu, 27 Sep 2007, Oliver Neukum wrote: > Hi, > > doing autosuspend for the storage driver, this feature was a sore point. > At some point we have to cross subsystem borders when doing runtime > suspend on a subtree of the device tree. Drivers need to know whether > they are doing a system wide suspend or a runtime suspend. The locking > requirements at the very least are different. > We need a standardised way to tell drivers what kind of suspension they > are dealing with. So I think it has to move into the generic struct device > or become a part of the message parameter. If it goes anywhere, it ought to be in the message parameter. My reason for putting it in struct usb_device originally was because there was no other choice at the time. 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. Alan Stern _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
