On Friday 23 September 2011 23:00:41 Dmitry Torokhov wrote: > The application will get an error on read or write, like -ENODEV, and will > hopefully "drop off". Thank you for the answer, but I would still like to avoid zapping the input device runtime for now. In order to do that, I need to build up some sort of notification infra for the twl6040 vibra (in the MFD driver) to create, and destroy the input device depending on the changes in the audio driver. I'm also concerned about the needed LOC for this to implement, might be too overkill, since I would think that the twl6040 vibra driving method would not change runtime in any system. As a note: the other vibra (twl4030-vibra) does not even let user space know, that it ignored the effect due to the routing selection. Returning -EBUSY is a bit better than that.. I know this is not a valid argument for anything ;) Regards, Péter -- 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
