On Mon, Sep 06, 2010 at 10:30:05AM -0400, Alan Stern wrote: > The real issue with USB interfaces is that they are only logical > sub-devices; they can't be power-managed separately from their parent. > Indeed, the runtime_suspend and runtime_resume callbacks for interfaces > always return 0 immediately without doing anything, and the > runtime_idle callback always calls pm_runtime_suspend. > So why not tell the PM core about this behavior? Let's put a > "no_callbacks" flag in dev_pm_info. When this flag is set the core > won't bother invoking the runtime callbacks; it can always assume > success. More importantly, an asynchronous request may never need to > use the workqueue: ... > Does that look like what you're talking about? That'd cover my use case, though it would still be nice to have the flexibility to just omit individual callbacks in the same way that it's possible to do so with regular suspend and resume (eg, if you only have to restore some state after the bus has suspended your device). -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
