Lines Matching +full:off +full:- +full:by

2 rfkill - RF kill switch support
18 situations where transmitters need to be turned off, for example on
22 differ little in their meaning (block == transmitters off) but rather in
25  - hard block
26 	read-only radio block that cannot be overridden by software
28  - soft block
29 	writable radio block (need not be readable) that is set by
34 admin-guide/kernel-parameters.rst.
43  * the deprecated rfkill-input module (an input layer handler, being
44    replaced by userspace policy code) and
48 transmitter with the kernel, methods for turning it on and off, and letting
49 the system know about hardware-disabled states that may be implemented on
56 When the device is hard-blocked (either by a call to rfkill_set_hw_state()
73 a way to turn on/off the transmitter(s).
83 to ensure the driver cannot be built-in when rfkill is modular. The !RFKILL
85 case all rfkill API can still be used but will be provided by static inlines
89 rfkill drivers that control devices that can be hard-blocked unless they also
93 rfkill provides per-switch LED triggers, which can be used to drive LEDs
104 linux/rfkill.h, with one ioctl that allows turning off the deprecated input
116 devices. Changes can be obtained by either polling the descriptor for
117 hotplug or state change events or by listening for uevents emitted by the
132 For further details consult Documentation/ABI/stable/sysfs-class-rfkill.