| commit | 526324b61a9667ed9a71f0a8a8899cf675346c76 | |
| author | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | |
| Mon, 23 Jun 2008 20:23:02 +0000 (23 17:23 -0300) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Thu, 26 Jun 2008 18:21:20 +0000 (26 14:21 -0400) | ||
| tree | 4a7697c0987ab4869f2760f06e1ba8e487a91af8 | treesnapshot (tar.gz zip) |
| parent | 477576a073699783abb53ae14993d5d41c66301d | commitdiff |
rfkill: rework suspend and resume handlers
The resume handler should reset the wireless transmitter rfkill
state to exactly what it was when the system was suspended. Do it,
and do it using the normal routines for state change while at it.
The suspend handler should force-switch the transmitter to blocked
state, ignoring caches. Do it.
Also take an opportunity shot to rfkill_remove_switch() and also
force the transmitter to blocked state there, bypassing caches.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
The resume handler should reset the wireless transmitter rfkill
state to exactly what it was when the system was suspended. Do it,
and do it using the normal routines for state change while at it.
The suspend handler should force-switch the transmitter to blocked
state, ignoring caches. Do it.
Also take an opportunity shot to rfkill_remove_switch() and also
force the transmitter to blocked state there, bypassing caches.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| net/rfkill/rfkill.c | diffblobblamehistory |