On Thursday 26 November 2009, Oliver Neukum wrote: > Hi, > > using the USB autosuspend framework I've often faced characteristic > problems coding resume() methods. This has led me to an idea. Resume() > would be much easier to code if I knew about the reason of resumption, > especially about the code path resume() is called in. I wonder whether > we could introduce a message argument to resume and give it a few > bits from the caller. Each of the callbacks in struct dev_pm_ops is executed in exactly one context, so for each of them it is known why it was called. Thanks, Rafael _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
