Hi Mario, > > I'm really still not quite clear on what the issue here is. At boot, > > there are hid devices that need to be quirked into hci mode. Over > > suspend these devices return to their original state. So something needs > > to be done to quirk them back on resume. Why is this a kernel issue at > > all? > > > > > At boot, the top level device exposes two virtual HID devices. A > userspace utility prods one of the HID devices and then the top level > device exposes an HCI device. Upon S3/resume, a reset-resume happens, > and the HCI device is gone. The system thinks that they are in the same > state after S3 (with the exception of the missing HCI device) so a UDEV > ADD or CHANGE event doesn't happen. if this is about the uevent issue again, then RFKILL is not the solution for it. This should be fixed completely in userspace. Regards Marcel -- 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
