Loading...
1# SPDX-License-Identifier: GPL-2.0-only
2config IWLWIFI
3 tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi) "
4 depends on PCI && HAS_IOMEM && CFG80211
5 depends on IWLMEI || !IWLMEI
6 select FW_LOADER
7 help
8 Select to build the driver supporting the:
9
10 Intel Wireless WiFi Link Next-Gen AGN
11
12 This option enables support for use with the following hardware:
13 Intel Wireless WiFi Link 6250AGN Adapter
14 Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
15 Intel WiFi Link 1000BGN
16 Intel Wireless WiFi 5150AGN
17 Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
18 Intel 6005 Series Wi-Fi Adapters
19 Intel 6030 Series Wi-Fi Adapters
20 Intel Wireless WiFi Link 6150BGN 2 Adapter
21 Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
22 Intel 2000 Series Wi-Fi Adapters
23 Intel 7260 Wi-Fi Adapter
24 Intel 3160 Wi-Fi Adapter
25 Intel 7265 Wi-Fi Adapter
26 Intel 8260 Wi-Fi Adapter
27 Intel 3165 Wi-Fi Adapter
28
29
30 This driver uses the kernel's mac80211 subsystem.
31
32 In order to use this driver, you will need a firmware
33 image for it. You can obtain the microcode from:
34
35 <https://wireless.wiki.kernel.org/en/users/Drivers/iwlwifi>.
36
37 The firmware is typically installed in /lib/firmware. You can
38 look in the hotplug script /etc/hotplug/firmware.agent to
39 determine which directory FIRMWARE_DIR is set to when the script
40 runs.
41
42 If you want to compile the driver as a module ( = code which can be
43 inserted in and removed from the running kernel whenever you want),
44 say M here and read <file:Documentation/kbuild/modules.rst>. The
45 module will be called iwlwifi.
46
47if IWLWIFI
48
49config IWLWIFI_LEDS
50 bool
51 depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211
52 depends on IWLMVM || IWLDVM
53 select LEDS_TRIGGERS
54 select MAC80211_LEDS
55 default y
56
57config IWLDVM
58 tristate "Intel Wireless WiFi DVM Firmware support"
59 depends on MAC80211
60 help
61 This is the driver that supports the DVM firmware. The list
62 of the devices that use this firmware is available here:
63 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
64
65config IWLMVM
66 tristate "Intel Wireless WiFi MVM Firmware support"
67 select WANT_DEV_COREDUMP
68 depends on MAC80211
69 depends on PTP_1588_CLOCK_OPTIONAL
70 help
71 This is the driver that supports the MVM firmware. The list
72 of the devices that use this firmware is available here:
73 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
74
75# don't call it _MODULE -- will confuse Kconfig/fixdep/...
76config IWLWIFI_OPMODE_MODULAR
77 bool
78 default y if IWLDVM=m
79 default y if IWLMVM=m
80
81comment "WARNING: iwlwifi is useless without IWLDVM or IWLMVM"
82 depends on IWLDVM=n && IWLMVM=n
83
84menu "Debugging Options"
85
86config IWLWIFI_DEBUG
87 bool "Enable full debugging output in the iwlwifi driver"
88 help
89 This option will enable debug tracing output for the iwlwifi drivers
90
91 This will result in the kernel module being ~100k larger. You can
92 control which debug output is sent to the kernel log by setting the
93 value in
94
95 /sys/module/iwlwifi/parameters/debug
96
97 This entry will only exist if this option is enabled.
98
99 To set a value, simply echo an 8-byte hex value to the same file:
100
101 % echo 0x43fff > /sys/module/iwlwifi/parameters/debug
102
103 You can find the list of debug mask values in:
104 drivers/net/wireless/iwlwifi/iwl-debug.h
105
106 If this is your first time using this driver, you should say Y here
107 as the debug information can assist others in helping you resolve
108 any problems you may encounter.
109
110config IWLWIFI_DEBUGFS
111 bool "iwlwifi debugfs support"
112 depends on MAC80211_DEBUGFS
113 help
114 Enable creation of debugfs files for the iwlwifi drivers. This
115 is a low-impact option that allows getting insight into the
116 driver's state at runtime.
117
118config IWLWIFI_DEVICE_TRACING
119 bool "iwlwifi device access tracing"
120 depends on EVENT_TRACING
121 default y
122 help
123 Say Y here to trace all commands, including TX frames and IO
124 accesses, sent to the device. If you say yes, iwlwifi will
125 register with the ftrace framework for event tracing and dump
126 all this information to the ringbuffer, you may need to
127 increase the ringbuffer size. See the ftrace documentation
128 for more information.
129
130 When tracing is not enabled, this option still has some
131 (though rather small) overhead.
132
133 If unsure, say Y so we can help you better when problems
134 occur.
135endmenu
136
137endif
138
139config IWLMEI
140 tristate "Intel Management Engine communication over WLAN"
141 depends on INTEL_MEI
142 depends on PM
143 depends on CFG80211
144 depends on BROKEN
145 help
146 Enables the iwlmei kernel module.
147
148 CSME stands for Converged Security and Management Engine. It is a CPU
149 on the chipset and runs a dedicated firmware. AMT (Active Management
150 Technology) is one of the applications that run on that CPU. AMT
151 allows to control the platform remotely.
152
153 This kernel module allows to communicate with the Intel Management
154 Engine over Wifi. This is supported starting from Tiger Lake
155 platforms and has been tested on 9260 devices only.
156 If AMT is configured not to use the wireless device, this module is
157 harmless (and useless).
158 Enabling this option on a platform that has a different device and
159 has Wireless enabled on AMT can prevent WiFi from working correctly.
160
161 For more information see
162 <https://software.intel.com/en-us/manageability/>
163
164 If unsure, say N.
1# SPDX-License-Identifier: GPL-2.0-only
2config IWLWIFI
3 tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi) "
4 depends on PCI && HAS_IOMEM && CFG80211
5 select FW_LOADER
6 help
7 Select to build the driver supporting the:
8
9 Intel Wireless WiFi Link Next-Gen AGN
10
11 This option enables support for use with the following hardware:
12 Intel Wireless WiFi Link 6250AGN Adapter
13 Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
14 Intel WiFi Link 1000BGN
15 Intel Wireless WiFi 5150AGN
16 Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
17 Intel 6005 Series Wi-Fi Adapters
18 Intel 6030 Series Wi-Fi Adapters
19 Intel Wireless WiFi Link 6150BGN 2 Adapter
20 Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
21 Intel 2000 Series Wi-Fi Adapters
22 Intel 7260 Wi-Fi Adapter
23 Intel 3160 Wi-Fi Adapter
24 Intel 7265 Wi-Fi Adapter
25 Intel 8260 Wi-Fi Adapter
26 Intel 3165 Wi-Fi Adapter
27
28
29 This driver uses the kernel's mac80211 subsystem.
30
31 In order to use this driver, you will need a firmware
32 image for it. You can obtain the microcode from:
33
34 <https://wireless.wiki.kernel.org/en/users/Drivers/iwlwifi>.
35
36 The firmware is typically installed in /lib/firmware. You can
37 look in the hotplug script /etc/hotplug/firmware.agent to
38 determine which directory FIRMWARE_DIR is set to when the script
39 runs.
40
41 If you want to compile the driver as a module ( = code which can be
42 inserted in and removed from the running kernel whenever you want),
43 say M here and read <file:Documentation/kbuild/modules.rst>. The
44 module will be called iwlwifi.
45
46if IWLWIFI
47
48config IWLWIFI_LEDS
49 bool
50 depends on LEDS_CLASS=y || LEDS_CLASS=IWLWIFI
51 depends on IWLMVM || IWLDVM
52 select LEDS_TRIGGERS
53 select MAC80211_LEDS
54 default y
55
56config IWLDVM
57 tristate "Intel Wireless WiFi DVM Firmware support"
58 depends on MAC80211
59 help
60 This is the driver that supports the DVM firmware. The list
61 of the devices that use this firmware is available here:
62 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
63
64config IWLMVM
65 tristate "Intel Wireless WiFi MVM Firmware support"
66 select WANT_DEV_COREDUMP
67 depends on MAC80211
68 help
69 This is the driver that supports the MVM firmware. The list
70 of the devices that use this firmware is available here:
71 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
72
73# don't call it _MODULE -- will confuse Kconfig/fixdep/...
74config IWLWIFI_OPMODE_MODULAR
75 bool
76 default y if IWLDVM=m
77 default y if IWLMVM=m
78
79comment "WARNING: iwlwifi is useless without IWLDVM or IWLMVM"
80 depends on IWLDVM=n && IWLMVM=n
81
82config IWLWIFI_BCAST_FILTERING
83 bool "Enable broadcast filtering"
84 depends on IWLMVM
85 help
86 Say Y here to enable default bcast filtering configuration.
87
88 Enabling broadcast filtering will drop any incoming wireless
89 broadcast frames, except some very specific predefined
90 patterns (e.g. incoming arp requests).
91
92 If unsure, don't enable this option, as some programs might
93 expect incoming broadcasts for their normal operations.
94
95menu "Debugging Options"
96
97config IWLWIFI_DEBUG
98 bool "Enable full debugging output in the iwlwifi driver"
99 help
100 This option will enable debug tracing output for the iwlwifi drivers
101
102 This will result in the kernel module being ~100k larger. You can
103 control which debug output is sent to the kernel log by setting the
104 value in
105
106 /sys/module/iwlwifi/parameters/debug
107
108 This entry will only exist if this option is enabled.
109
110 To set a value, simply echo an 8-byte hex value to the same file:
111
112 % echo 0x43fff > /sys/module/iwlwifi/parameters/debug
113
114 You can find the list of debug mask values in:
115 drivers/net/wireless/iwlwifi/iwl-debug.h
116
117 If this is your first time using this driver, you should say Y here
118 as the debug information can assist others in helping you resolve
119 any problems you may encounter.
120
121config IWLWIFI_DEBUGFS
122 bool "iwlwifi debugfs support"
123 depends on MAC80211_DEBUGFS
124 help
125 Enable creation of debugfs files for the iwlwifi drivers. This
126 is a low-impact option that allows getting insight into the
127 driver's state at runtime.
128
129config IWLWIFI_DEVICE_TRACING
130 bool "iwlwifi device access tracing"
131 depends on EVENT_TRACING
132 default y
133 help
134 Say Y here to trace all commands, including TX frames and IO
135 accesses, sent to the device. If you say yes, iwlwifi will
136 register with the ftrace framework for event tracing and dump
137 all this information to the ringbuffer, you may need to
138 increase the ringbuffer size. See the ftrace documentation
139 for more information.
140
141 When tracing is not enabled, this option still has some
142 (though rather small) overhead.
143
144 If unsure, say Y so we can help you better when problems
145 occur.
146endmenu
147
148endif