On Wed, 20 May 2009, Mario Limonciello wrote: > Hi Alan: > > Alan Stern wrote: > > On Wed, 20 May 2009, Oliver Neukum wrote: > > > > > > > > That's okay. Inelegant, perhaps, but workable. Besides, as we see > > below, the new rule would have to do more than the old rule. > > > > > I agree this is a rather inelegant solution. A new rule would have to > be added to hid2hci then. It's much more preferable to be able to fix > kernel space from mucking up the device. Is there a way to mark a > device to /not/ run reset-resume after S3? echo 0 >/sys/bus/usb/devices/.../power/persist This will also prevent reset-resume after hibernation. > > Does that create the same removal event? If it does then you wouldd be > > in an unfortunate state. The script would have to check somehow > > whether the removal was deliberate or spontaneous. > > > Yes it does create the same removal event when you switch to HID mode. > I don't know of any way that you can calculate if the switch was > intentional. You can't. Instead you have to arrange things so that when the intentional change was made, it left behind a timestamp indicator. If that timestamp if present and not more than a few seconds in the past, you know the change was intentional. 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
