Am Mittwoch, 29. Oktober 2008 14:28:12 schrieb Jiri Kosina: > On Mon, 27 Oct 2008, Oliver Neukum wrote: > > > This uses the USB busy mechanism for aggessive autosuspend of USB HID > > devices. It autosuspends all opened devices supporting remote wakeup > > after a timeout unless > > > > - output is being done to the device > > - a key is being held down (remote wakeup isn't triggered upon key release) > > - LED(s) are lit > > - hiddev is opened > > Hi Oliver, > > doesn't hidraw (the generic transport-independent variant of > USB-specific hiddev) need also some handling? Good point. Yes, it does. This leaves me with two problems. 1. The HID API doesn't tell me why a device is opened. Add a flag? 2. hidraw calls open with a spinlock held. I suggest converting it to a mutex. What do you think? Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
