On Mon, 16 Jul 2012, Lan Tianyu wrote: > Currently, "power/wakeup" sysfs file can't control remote wakeup in the runtime > suspend. It only depends on "usb_interface->needs_remote_wakeup" to determine > whether enable remote wakeup or not when runtime suspending. Usr space has no > choice. This patch is to enable "power/wakeup" to control remote wakeup in the > runtime suspend. As Oliver pointed out, you need to explain why this is needed. More importantly, the patch is completely wrong. The "power/wakeup" parameter is not meant for controlling runtime resume; it is supposed to be used only for system resume. Yes, userspace has no choice about wakeup during runtime suspend. It is controlled entirely by the driver. If userspace wants to change the settings, it has to inform the driver somehow. But why would userspace want to change the setting? 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
