As requested by Henrique, I have reworked this patch against wireless-testing and it uses the new-style rfkill API and to report the input device as a switch. I did some digging to try and find a usable gpe event but had only limited success. From another look through the AML, it uses GPE08 for almost everything - inspecting a bunch of state for each event and then sending notifications on different objects. I couldn't find one for the hardware kill switch itself but I did manage to find one that's emitted when the bluetooth device enters the equivalent of the SOFT_BLOCKED state. This is useful for noticing that the hardware switch has been released, but it also fires on transitions from UNBLOCKED to SOFT_BLOCKED - so I had to try and avoid turning around and unblocking the device! I'm not particularly happy with how I did it (ignore-the-next-event) but I can't think of a better way. --phil -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
