Hi Mario, > > what are you trying to solve here. And why do you need to disable a > > Bluetooth radio on suspend? Are you trying to hack around a bug? > > The problem is that a reset-resume is being ran on the BT radio device > as well as the two virtual HID devices. So the OS thinks that the BT > radio device is still there after resuming from S3, but it isn't as the > hardware is then in a different state after S3. > > The initial solution I proposed was in the dell_laptop kernel module to > run turn off/on explicitly using the rfkill interface that dell_laptop > creates, but that not a good solution so Alan proposed adding something > to userspace to run when the BT radio disappears but that the rest of > the virtual HID devices are still there. you know that we re-wrote RFKILL completely. You can kill a Bluetooth device from within the kernel. And this looks like a hardkill of the Bluetooth interface. The only think that you can't do is send input events around to trigger RFKILL. That is broken and will be removed. 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
