Skip to contentSkip to conversation

toshiba_acpi: Support RFKILL hotkey scancode

PATCH In review Unai Uribarri 2 participants 3 messages Jan 14, 2014 – Jan 15, 2014

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 toshiba_acpi: Support RFKILL hotkey scancode

This scancode is used in new 2013 models like Satellite P75-A7200.

---
 drivers/platform/x86/toshiba_acpi.c |    1 +
 1 file changed, 1 insertion(+)
drivers/platform/x86/toshiba_acpi.c +1 -0
index 7fce391..5d23ca2 100644
@@ -151,6 +151,7 @@ static const struct acpi_device_id toshiba_device_ids[] = {
 MODULE_DEVICE_TABLE(acpi, toshiba_device_ids);
 
 static const struct key_entry toshiba_acpi_keymap[] = {
+	{ KE_KEY, 0x9e, { KEY_RFKILL } },
 	{ KE_KEY, 0x101, { KEY_MUTE } },
 	{ KE_KEY, 0x102, { KEY_ZOOMOUT } },
 	{ KE_KEY, 0x103, { KEY_ZOOMIN } },
Signature · 1 line
1.7.9.5
#1 lore raw
Quoted 1 line · Unai Uribarri

This scancode is used in new 2013 models like Satellite P75-A7200.

Just to check - this is generated by a key that otherwise does nothing, right? Ie, hitting the key generates the scancode but doesn't automatically change the wireless state?

Signature · 1 line
Matthew Garrett <[email protected]>
#2 lore raw

In Windows disables the Wi-Fi & Bluetooth. In Linux does nothing but showing this error in dmesg about the unrecognized scancode:

[230128.042047] toshiba_acpi: Unknown key 158
Quoted 9 lines · Matthew Garrett
Quoted 1 line · Unai Uribarri

This scancode is used in new 2013 models like Satellite P75-A7200.

Just to check - this is generated by a key that otherwise does nothing, right? Ie, hitting the key generates the scancode but doesn't automatically change the wireless state?

--
Matthew Garrett <[email protected]>