toshiba_acpi: Add support for bluetooth toggling through rfkill
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 1 patch 2 repliesIn review
Patches in v1 No applies recorded yet
The patch the cover letter announces is not in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1] toshiba_acpi: Add support for bluetooth toggling through rfkill
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