| commit | 6e28fbef0f330d7c1cade345eeae003d4e5d6070 | |
| author | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | |
| Thu, 31 Jul 2008 13:53:57 +0000 (31 10:53 -0300) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Fri, 1 Aug 2008 19:31:32 +0000 (1 15:31 -0400) | ||
| tree | 69d5f4e32a6ed95eb2bdc89678ca87d60274d2fb | treesnapshot (tar.gz zip) |
| parent | f860ee26db51c478fd70039bd4902912a8d93993 | commitdiff |
rfkill: query EV_SW states when rfkill-input (re)?connects to a input device
Every time a new input device that is capable of one of the
rfkill EV_SW events (currently only SW_RFKILL_ALL) is connected to
rfkill-input, we must check the states of the input EV_SW switches
and take action. Otherwise, we will ignore the initial switch state.
We also need to re-check the states of the EV_SW switches after
a device that was under an exclusive grab is released back to us,
since we got no input events from that device while it was grabbed.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
Cc: Dmitry Torokhov <dtor@mail.ru>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Every time a new input device that is capable of one of the
rfkill EV_SW events (currently only SW_RFKILL_ALL) is connected to
rfkill-input, we must check the states of the input EV_SW switches
and take action. Otherwise, we will ignore the initial switch state.
We also need to re-check the states of the EV_SW switches after
a device that was under an exclusive grab is released back to us,
since we got no input events from that device while it was grabbed.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
Cc: Dmitry Torokhov <dtor@mail.ru>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| net/rfkill/rfkill-input.c | diffblobblamehistory |