1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi) "
4 depends on PCI && HAS_IOMEM && CFG80211
7 Select to build the driver supporting the:
9 Intel Wireless WiFi Link Next-Gen AGN
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
29 This driver uses the kernel's mac80211 subsystem.
31 In order to use this driver, you will need a firmware
32 image for it. You can obtain the microcode from:
34 <https://wireless.wiki.kernel.org/en/users/Drivers/iwlwifi>.
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
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.
50 depends on LEDS_CLASS=y || LEDS_CLASS=IWLWIFI
51 depends on IWLMVM || IWLDVM
57 tristate "Intel Wireless WiFi DVM Firmware support"
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
65 tristate "Intel Wireless WiFi MVM Firmware support"
66 select WANT_DEV_COREDUMP
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
73 # don't call it _MODULE -- will confuse Kconfig/fixdep/...
74 config IWLWIFI_OPMODE_MODULAR
79 comment "WARNING: iwlwifi is useless without IWLDVM or IWLMVM"
80 depends on IWLDVM=n && IWLMVM=n
82 config IWLWIFI_BCAST_FILTERING
83 bool "Enable broadcast filtering"
86 Say Y here to enable default bcast filtering configuration.
88 Enabling broadcast filtering will drop any incoming wireless
89 broadcast frames, except some very specific predefined
90 patterns (e.g. incoming arp requests).
92 If unsure, don't enable this option, as some programs might
93 expect incoming broadcasts for their normal operations.
95 menu "Debugging Options"
98 bool "Enable full debugging output in the iwlwifi driver"
100 This option will enable debug tracing output for the iwlwifi drivers
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
106 /sys/module/iwlwifi/parameters/debug
108 This entry will only exist if this option is enabled.
110 To set a value, simply echo an 8-byte hex value to the same file:
112 % echo 0x43fff > /sys/module/iwlwifi/parameters/debug
114 You can find the list of debug mask values in:
115 drivers/net/wireless/iwlwifi/iwl-debug.h
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.
121 config IWLWIFI_DEBUGFS
122 bool "iwlwifi debugfs support"
123 depends on MAC80211_DEBUGFS
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.
129 config IWLWIFI_DEVICE_TRACING
130 bool "iwlwifi device access tracing"
131 depends on EVENT_TRACING
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.
141 When tracing is not enabled, this option still has some
142 (though rather small) overhead.
144 If unsure, say Y so we can help you better when problems