blob: 598d374f6a35f714db4753efa7ab28d6782419a9 [file] [log] [blame]
Kyle Swenson8d8f6542021-03-15 11:02:55 -06001#
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
13# LED trigger support
14config RFKILL_LEDS
15 bool
16 depends on RFKILL
17 depends on LEDS_TRIGGERS = y || RFKILL = LEDS_TRIGGERS
18 default y
19
20config RFKILL_INPUT
21 bool "RF switch input support" if EXPERT
22 depends on RFKILL
23 depends on INPUT = y || RFKILL = INPUT
24 default y if !EXPERT
25
26config RFKILL_REGULATOR
27 tristate "Generic rfkill regulator driver"
28 depends on RFKILL || !RFKILL
29 depends on REGULATOR
30 help
31 This options enable controlling radio transmitters connected to
32 voltage regulator using the regulator framework.
33
34 To compile this driver as a module, choose M here: the module will
35 be called rfkill-regulator.
36
37config RFKILL_GPIO
38 tristate "GPIO RFKILL driver"
39 depends on RFKILL
40 depends on GPIOLIB || COMPILE_TEST
41 default n
42 help
43 If you say yes here you get support of a generic gpio RFKILL
44 driver. The platform should fill in the appropriate fields in the
45 rfkill_gpio_platform_data structure and pass that to the driver.