blob: 8e12c8a2b82b613a5637537685b71174c412c028 [file] [log] [blame]
lh9ed821d2023-04-07 01:36:19 -07001#
2# RF switch subsystem configuration
3#
4menuconfig RFKILL
5 tristate "RF switch subsystem support"
6 help
7 Say Y here if you want to have control over RF switches
8 found on many WiFi and Bluetooth cards.
9
10 To compile this driver as a module, choose M here: the
11 module will be called rfkill.
12
13config RFKILL_PM
14 bool "Power off on suspend"
15 depends on RFKILL && PM
16 default y
17
18# LED trigger support
19config RFKILL_LEDS
20 bool
21 depends on RFKILL
22 depends on LEDS_TRIGGERS = y || RFKILL = LEDS_TRIGGERS
23 default y
24
25config RFKILL_INPUT
26 bool "RF switch input support" if EXPERT
27 depends on RFKILL
28 depends on INPUT = y || RFKILL = INPUT
29 default y if !EXPERT
30
31config RFKILL_REGULATOR
32 tristate "Generic rfkill regulator driver"
33 depends on RFKILL || !RFKILL
34 depends on REGULATOR
35 help
36 This options enable controlling radio transmitters connected to
37 voltage regulator using the regulator framework.
38
39 To compile this driver as a module, choose M here: the module will
40 be called rfkill-regulator.
41
42config RFKILL_GPIO
43 tristate "GPIO RFKILL driver"
44 depends on RFKILL && GPIOLIB && HAVE_CLK
45 default n
46 help
47 If you say yes here you get support of a generic gpio RFKILL
48 driver. The platform should fill in the appropriate fields in the
49 rfkill_gpio_platform_data structure and pass that to the driver.