On Sat, 15 Aug 2009, Rafael J. Wysocki wrote: > > Why would you ever want runtime_wakeup to be false unless > > runtime_forbidden is true? Surely the point of runtime power management > > is to be transparent to the user, in which case remote wakeup is > > required? Matthew, what makes you think remote wakeup is required? Lots of power-manageable devices don't support it at all (consider disk drives or display screens). > Well, this was exactly my point previously. :-) > > Still, although for the majority of devices 'runtime_wakeup' disabled would > mean no runtime PM at all IMO, there may be devices that actually work without > remote wakeup, although they support it in general. That last part is quite true. For example, we might suspend the device whenever no process has opened the device file. It would be a degraded form of power management, but better than nothing. > I can even imagine a scenario where this setting might be useful, like when > we don't want a network adapter to be woken up from the outside. Or if the device's support for remote wakeup is broken. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
