Lines Matching refs:rfkill

1 rfkill - RF kill switch support
12 The rfkill subsystem provides a generic interface to disabling any radio
21 The rfkill subsystem has a concept of "hard" and "soft" block, which
28 The rfkill subsystem has two parameters, rfkill.default_state and
29 rfkill.master_switch_mode, which are documented in kernel-parameters.txt.
34 The rfkill subsystem is composed of three main components:
35  * the rfkill core,
36  * the deprecated rfkill-input module (an input layer handler, being
38  * the rfkill drivers.
40 The rfkill core provides API for kernel drivers to register their radio
45 The rfkill core code also notifies userspace of state changes, and provides
61 Drivers for radio transmitters normally implement an rfkill driver.
63 Platform drivers might implement input devices if the rfkill button is just
65 implement an rfkill driver instead. This also applies if the platform provides
69 suspend/hibernation, in which case it will be necessary to update the rfkill
72 To create an rfkill driver, driver's Kconfig needs to have
76 to ensure the driver cannot be built-in when rfkill is modular. The !RFKILL
77 case allows the driver to be built when rfkill is not configured, which
78 case all rfkill API can still be used but will be provided by static inlines
82 rfkill drivers that control devices that can be hard-blocked unless they also
83 assign the poll_hw_block() callback (then the rfkill core will poll the
90 The recommended userspace interface to use is /dev/rfkill, which is a misc
91 character device that allows userspace to obtain and set the state of rfkill
94 linux/rfkill.h, with one ioctl that allows turning off the deprecated input
100 userspace is able to get a consistent snapshot of all rfkill devices in the
101 system. Also, it is possible to switch all rfkill drivers (or all drivers of
105 After an application opens /dev/rfkill, it can read the current state of all
108 rfkill core framework.
110 Additionally, each rfkill device is registered in sysfs and emits uevents.
112 rfkill devices issue uevents (with an action of "change"), with the following
123 For further details consult Documentation/ABI/stable/sysfs-class-rfkill.