On Wed, 11 Nov 2009, Rafael J. Wysocki wrote: > > Now, this does raise another point, which has been mentioned before. > > To wit: devices really ought to have _two_ remote-wakeup attributes, > > one for runtime PM and one for system sleep. > > Yes, they do and there's another reason. Namely, there apparently are > devices which can wake up the system from a sleep state and that are > unable to generate runtime wakeup events. That's okay. There's no harm in trying to enable remote wakeup on a device which doesn't support it. > > But that would introduce yet more complexity and opportunities for > > confusion. > > Nevertheless. The real question is whether there are devices for which we explicitly want to enable remote wakeup during runtime PM but not system sleep (or vice versa, but this seems rather unlikely). USB host controllers might be a good example; as a rule people don't want their laptops to wake up when they unplug a USB mouse after suspending the machine. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
