Inaky Perez-Gonzalez c29eaf3fae wimax: indicate initial SW rfkill state is "blocked" ...

The WiMAX stack assumes that all WiMAX devices are SW OFF when they
are initialized. The recent changes in the RFKILL stack thus cause an
initial call after rfkill_register(), because by default, rfkill
considers devices to be SW ON upon registration.

So call rfkill_init_sw_state() to set it to SW OFF so
rfkill_register() doesn't do that unnecessary step.

Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>

2009-10-19 15:55:34 +09:00

..

debug-levels.h

wimax: Add netlink interface to get device state

2009-05-28 18:02:20 -07:00

debugfs.c

wimax: Add netlink interface to get device state

2009-05-28 18:02:20 -07:00

id-table.c

wimax: fix oops in wimax_dev_get_by_genl_info() when looking up non-wimax iface

2009-02-12 17:00:20 -08:00

Kconfig

wimax: depend on rfkill properly

2009-06-04 10:58:15 -04:00

Makefile

wimax: Add netlink interface to get device state

2009-05-28 18:02:20 -07:00

op-msg.c

wimax: document why wimax_msg_*() operations can be used in any state

2009-05-28 18:02:04 -07:00

op-reset.c

wimax: basic API: kernel/user messaging, rfkill and reset

2009-01-07 10:00:17 -08:00

op-rfkill.c

wimax: indicate initial SW rfkill state is "blocked"

2009-10-19 15:55:34 +09:00

op-state-get.c

wimax: Add netlink interface to get device state

2009-05-28 18:02:20 -07:00

stack.c

wimax: Add netlink interface to get device state

2009-05-28 18:02:20 -07:00

wimax-internal.h

…