Henrique de Moraes Holschuh f80b5e99c7 rfkill: preserve state across suspend ... The rfkill class API requires that the driver connected to a class call rfkill_force_state() on resume to update the real state of the rfkill controller, OR that it provides a get_state() hook. This means there is potentially a hidden call in the resume code flow that changes rfkill->state (i.e. rfkill_force_state()), so the previous state of the transmitter was being lost. The simplest and most future-proof way to fix this is to explicitly store the pre-sleep state on the rfkill structure, and restore from that on resume. Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br> Acked-by: Ivo van Doorn <IvDoorn@gmail.com> Cc: Matthew Garrett <mjg59@srcf.ucam.org> Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk> Signed-off-by: John W. Linville <linville@tuxdriver.com>		2008-11-26 09:47:43 -05:00
..
Kconfig	[RFKILL]: Add support for an rfkill LED.	2007-10-10 16:54:10 -07:00
Makefile	[NET]: rfkill: add support for input key to control wireless radio	2007-05-07 00:34:20 -07:00
rfkill-input.c	rfkill: rate-limit rfkill-input workqueue usage (v3)	2008-10-31 19:00:10 -04:00
rfkill-input.h	rfkill: add master_switch_mode and EPO lock to rfkill and rfkill-input	2008-10-31 19:00:09 -04:00
rfkill.c	rfkill: preserve state across suspend	2008-11-26 09:47:43 -05:00