On Fri, 1 Jun 2012, Steven Rostedt wrote: > > > Why do you want to skip the wakeup setting in that case? > > > > Because that's what the 151b61284776 commit did. Also, the quirk marks > > the controller as not wakeup-capable. > > > > Still, it's worth testing. Andrey and Steve, here's an updated patch > > which should leave wakeup enabled on your EHCI controllers. If you > > don't have a USB keyboard handy for generating a wakeup signal, you > > can test the wakeup functionality by doing: > > > > echo enabled >/sys/bus/usb/devices/usb1/power/wakeup > > echo enabled >/sys/bus/usb/devices/usb2/power/wakeup > > > > before suspending. (In fact you need only one of those two lines, but > > at the moment I forget which -- probably the usb2 one.) Then while > > the system is asleep, either plugging or unplugging a USB device > > directly into the computer should cause it to wake up. > > I applied the patch, it suspends and resumes fine, but still no wakeup. > > I even plugged in a USB keyboard, suspended, and tried to wake it up > with that. That did not work. I even enabled what you stated above, with > no effect (with keyboard or usb storage). This suggests that the original version of the patch is superior. There's not point in saying the controller is wakeup-capable and trying to enable wakeup if it's not going to work. 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
