path: root/Documentation/rfkill.txt
diff options
authorHenrique de Moraes Holschuh <hmh@hmh.eng.br>2008-08-02 14:56:25 -0300
committerJohn W. Linville <linville@tuxdriver.com>2008-08-18 11:05:12 -0400
commite10e0dfe3ba358cfb442cc3bf0d3f2068785bf5c (patch)
tree9921c44240e39f07bf825ede5777f72fbdfe40d0 /Documentation/rfkill.txt
parentaaa1553512b9105699113ea7e2ea726f3d9d4de2 (diff)
rfkill: protect suspended rfkill controllers
Guard rfkill controllers attached to a rfkill class against state changes after class suspend has been issued. 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>
Diffstat (limited to 'Documentation/rfkill.txt')
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/rfkill.txt b/Documentation/rfkill.txt
index 28b6ec87c642..6fcb3060dec5 100644
--- a/Documentation/rfkill.txt
+++ b/Documentation/rfkill.txt
@@ -363,6 +363,11 @@ This rule exists because users of the rfkill subsystem expect to get (and set,
when possible) the overall transmitter rfkill state, not of a particular rfkill
+5. During suspend, the rfkill class will attempt to soft-block the radio
+through a call to rfkill->toggle_radio, and will try to restore its previous
+state during resume. After a rfkill class is suspended, it will *not* call
+rfkill->toggle_radio until it is resumed.
Example of a WLAN wireless driver connected to the rfkill subsystem: