| commit | 92530664bbe5a13aede4a8763459bbe560ad9221 | |
| author | Seth Forshee <seth.forshee@canonical.com> | |
| Tue, 21 Jun 2011 17:00:33 +0000 (21 12:00 -0500) | ||
| committer | Matthew Garrett <mjg@redhat.com> | |
| Thu, 7 Jul 2011 14:38:56 +0000 (7 10:38 -0400) | ||
| tree | 8796470b6b0dcc74c0ce84ce556ea266172dde69 | treesnapshot (tar.gz zip) |
| parent | 4dd1b49c6d215dc41ce50c80b4868388b93f31a3 | commitdiff |
acer-wmi: Only update rfkill status for associated hotkey events
acer-wmi is indiscriminately using the device state from hotkey
events to update the various rfkill states. On the Aspire 1830 this
can result in a soft block on the wlan when the touchpad hotkey is
pressed, as it is reporting a non-zero device state that does not
reflect the wireless status. To fix this, only update rfkill states
when a wlan or bluetooth hotkey is pressed.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
Signed-off-by: Matthew Garrett <mjg@redhat.com>
acer-wmi is indiscriminately using the device state from hotkey
events to update the various rfkill states. On the Aspire 1830 this
can result in a soft block on the wlan when the touchpad hotkey is
pressed, as it is reporting a non-zero device state that does not
reflect the wireless status. To fix this, only update rfkill states
when a wlan or bluetooth hotkey is pressed.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
Signed-off-by: Matthew Garrett <mjg@redhat.com>
| drivers/platform/x86/acer-wmi.c | diffblobblamehistory |