RE: [DISCUSSION] USB device remote wakeup is not working for S3 case

[Alan Stern]

On Fri, 19 Dec 2014, Du, Changbin wrote:

> > There's a simple solution: Call device_set_wakeup_enable() for the device!
> > You can do this from the command line by:
> > 
> > 	echo auto >/sys/bus/usb/devices/.../power/control
> > 
> > where the "..." is the pathname for your device.
> > 
> Yes, this can enable auto-suspend for usb device like a mouse. And remote wakeup
> does work for RPM because rpm suspend refers to the needs_remote_wakeup flag.
> But this doesn't impact system level suspend. The correct thing is:
> 	
> 	echo enabled >/sys/bus/usb/devices/.../power/wakeup

Yes, I'm sorry, you're right.  It's easy to mix up autosuspend and 
wakeup.

> This will call device_set_wakeup_enable() for the device and should work. But 
> unfortunately it seems didn't work even the wakeup file shows "enabled" which 
> means the device is wakeup enabled(Tried on 3.16 & 3.18 kernel). This is a different
> issue, I will check.

You have to make sure that wakeup is also enabled for the host 
controller the device is attached to.  For some host controllers, it 
may also be necessary to enable wakeup for the root hub.

> Could we also enable wakeup for usb mouse? Or is there any concern to enable it?
> Per my opinion, most people may expect clicking mouse can awake system.

It doesn't matter to me, but you should ask the people on the 
linux-input mailing list.

Also, what about wakeup for a non-USB mouse?  Shouldn't that be enabled 
as well?

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/