rfkill: rewrite
This patch completely rewrites the rfkill core to address the following deficiencies: * all rfkill drivers need to implement polling where necessary rather than having one central implementation * updating the rfkill state cannot be done from arbitrary contexts, forcing drivers to use schedule_work and requiring lots of code * rfkill drivers need to keep track of soft/hard blocked internally -- the core should do this * the rfkill API has many unexpected quirks, for example being asymmetric wrt. alloc/free and register/unregister * rfkill can call back into a driver from within a function the driver called -- this is prone to deadlocks and generally should be avoided * rfkill-input pointlessly is a separate module * drivers need to #ifdef rfkill functions (unless they want to depend on or select RFKILL) -- rfkill should provide inlines that do nothing if it isn't compiled in * the rfkill structure is not opaque -- drivers need to initialise it correctly (lots of sanity checking code required) -- instead force drivers to pass the right variables to rfkill_alloc() * the documentation is hard to read because it always assumes the reader is completely clueless and contains way TOO MANY CAPS * the rfkill code needlessly uses a lot of locks and atomic operations in locked sections * fix LED trigger to actually change the LED when the radio state changes -- this wasn't done before Tested-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk> Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br> [thinkpad] Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
This commit is contained in:

committed by
John W. Linville

parent
0f6399c4c5
commit
19d337dff9
@@ -10,22 +10,15 @@ menuconfig RFKILL
|
||||
To compile this driver as a module, choose M here: the
|
||||
module will be called rfkill.
|
||||
|
||||
config RFKILL_INPUT
|
||||
tristate "Input layer to RF switch connector"
|
||||
depends on RFKILL && INPUT
|
||||
help
|
||||
Say Y here if you want kernel automatically toggle state
|
||||
of RF switches on and off when user presses appropriate
|
||||
button or a key on the keyboard. Without this module you
|
||||
need a some kind of userspace application to control
|
||||
state of the switches.
|
||||
|
||||
To compile this driver as a module, choose M here: the
|
||||
module will be called rfkill-input.
|
||||
|
||||
# LED trigger support
|
||||
config RFKILL_LEDS
|
||||
bool
|
||||
depends on RFKILL && LEDS_TRIGGERS
|
||||
depends on RFKILL
|
||||
depends on LEDS_TRIGGERS = y || RFKILL = LEDS_TRIGGERS
|
||||
default y
|
||||
|
||||
config RFKILL_INPUT
|
||||
bool
|
||||
depends on RFKILL
|
||||
depends on INPUT = y || RFKILL = INPUT
|
||||
default y
|
||||
|
Reference in New Issue
Block a user