On Wed, 7 Aug 2013, Huang Rui wrote: > > > Got it, but I'm still a little confused. For example, one mouse is > > > attached at usb2.0 port of roothub, and it supports remote wakeup. But > > > the wakeup attribute is disabled for mouse defaultly, am I right? So > > > > Yes. > > > > > remote wakeup doesn't work on this mouse, then run system suspend into > > > s3 with "global suspend"(don't send Set Suspend Feature request). In > > > this case, remote wakeup and global suspend doesn't mix, am I right? > > > > No. In this case they do mix okay. > > > > If use power button instead to wake up, is that mix? Or in other > cases? When I say they don't mix, I mean that remote wakeup doesn't always work properly when you use it with global suspend. > I use "ehco enabled > /sys/usb/bus/.../power/wakeup" to enable USB > Mouse remote wakeup, then sleep into S3. I found that wakeup attribute > is clear to be disabled after resume. Do you mean the attribute changes to "disabled" after resume? This is probably because the root hub lost power during the suspend. Check the dmesg log. > But if both USB Mouse and > Keyboard are attached on usb3.0 port and keep usb2.0 port no attached, > the wakeup attribute is remained. Could you kindly tell me why? Probably because the USB-3 controller did not lose power during the suspend. 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
