Am Mittwoch, 4. Juli 2007 schrieb Alan Stern: > Here's a question that has been bothering me for a while. Should we > enable remote wakeup on USB hubs? > > On the face of it the answer is obviously Yes. And certainly we want > remote wakeup enabled during a runtime suspend; otherwise the system > would never know when the user unplugged a device from the hub or > plugged in a new one. I agree. Runtime suspend needs remote wakeup. > But consider STR, say in the case of a laptop with a USB mouse > attached. The user suspends the laptop. Then he prepares to pack it > away and in the process unplugs the mouse. Pow! -- the laptop > springs back to life. That's not what we want. We might want attaching a device to wake the laptop. OR we might not. The choice is not makeable in kernel space. > On the other hand, the user might indeed want to awaken the laptop by > clicking the USB mouse. So what should we do? The question is made > even more difficult by the fact that, if the hub is already > runtime-suspended when the system suspend occurs, we would have to > resume the hub just in order to turn off remote wakeup! I don't think this can be helped. We cannot leave the setting of remote wakeup in the STR case to chance. We'd do so if we let stand the setting caused by autosuspend. If that means waking up a hub about to be suspended again, so be it. > Right now we more or less ignore all these issues by relying on the > wakeup settings in sysfs. Is that a reasonable approach? Is there > anything else we can do? I don't think so. It is the most reasonable approach. Regards Oliver _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
