On Wed, Apr 22, 2015 at 02:22:44PM -0400, Alan Stern wrote: > On Wed, 22 Apr 2015, Greg KH wrote: > > > > > But this device isn't always a keyboard. For example, mine works with a > > > > mouse. It's a "universal receiver", you can't know what type of HID > > > > device is plugged into it until it connects to it. I don't mind making > > > > it auto wakeup, if that works, but the comment isn't correct. > > > > > > Oh, okay, I didn't realize that. > > > > > > Is there a reasonable way to enable wakeup only when the driver learns > > > that a keyboard is connected? Where would the driver do this? > > > > I don't know if the driver ever "knows" this, as you can pair lots of > > different devices to this same receiver. There's a userspace > > application that lets you manage the device, called "solaar", that this > > option could be changed in. > > > > But really, putting the device to sleep should work for it no matter if > > this is a keyboard or a mouse or a joystick, as the wakeup logic is in > > the receiver, not in the device on the other end of the wireless link. > > > > Turning autosuspend works for me for my mouse connected. It doesn't > > work for one of my "real" USB keyboards when it's connected to the > > machine, which is why I can't enable autosuspend for it, as it drives me > > crazy. > > > > I don't have a keyboard to test the receiver with at the moment, to see > > if autosuspend works for both things connected at the same time, or for > > just the keyboard. > > Tom and I have been talking about enabling wakeup, not autosuspend. > The question is whether or not the default wakeup setting for the > receiver should be "enabled". Oh nevermind, sorry about that. > The kernel's policy is that keyboards should be enabled for wakeup, by > default. I think that matches most people's expectations. But when > you've got a "universal" receiver, what then? > > Should it always be enabled by default because a keyboard _might_ be > connected? Should it be enabled only when a keyboard is detected? > What if multiple devices are connected at the same time? > > Shucks -- does the receiver even _work_ as a wakeup device? It claims > to, but that would require it to remain in wireless contact with the > remote keyboard even while it's supposed to be in a low-power state, > which rather seems to defeat the purpose. I just tried it with my mouse connected, it didn't wake it up. Couldn't tell if it stayed connected to the mouse or not. > PS: I've got wakeup enabled for the PS/2 keyboard attached to the > computer I'm using now, but it doesn't work. I have to press the power > button to wake the machine up from suspend. Probably an issue in the > BIOS or ACPI -- I haven't bothered to try and track it down. Same here for my USB keyboard, it doesn't wake the machine up either... greg k-h -- 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
