xref: /linux/drivers/net/wireless/intel/iwlwifi/Kconfig (revision c6fbb759)
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	help
70	  This is the driver that supports the MVM firmware. The list
71	  of the devices that use this firmware is available here:
72	  https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
73
74# don't call it _MODULE -- will confuse Kconfig/fixdep/...
75config IWLWIFI_OPMODE_MODULAR
76	bool
77	default y if IWLDVM=m
78	default y if IWLMVM=m
79
80comment "WARNING: iwlwifi is useless without IWLDVM or IWLMVM"
81	depends on IWLDVM=n && IWLMVM=n
82
83menu "Debugging Options"
84
85config IWLWIFI_DEBUG
86	bool "Enable full debugging output in the iwlwifi driver"
87	help
88	  This option will enable debug tracing output for the iwlwifi drivers
89
90	  This will result in the kernel module being ~100k larger.  You can
91	  control which debug output is sent to the kernel log by setting the
92	  value in
93
94		/sys/module/iwlwifi/parameters/debug
95
96	  This entry will only exist if this option is enabled.
97
98	  To set a value, simply echo an 8-byte hex value to the same file:
99
100		  % echo 0x43fff > /sys/module/iwlwifi/parameters/debug
101
102	  You can find the list of debug mask values in:
103		  drivers/net/wireless/iwlwifi/iwl-debug.h
104
105	  If this is your first time using this driver, you should say Y here
106	  as the debug information can assist others in helping you resolve
107	  any problems you may encounter.
108
109config IWLWIFI_DEBUGFS
110	bool "iwlwifi debugfs support"
111	depends on MAC80211_DEBUGFS
112	help
113	  Enable creation of debugfs files for the iwlwifi drivers. This
114	  is a low-impact option that allows getting insight into the
115	  driver's state at runtime.
116
117config IWLWIFI_DEVICE_TRACING
118	bool "iwlwifi device access tracing"
119	depends on EVENT_TRACING
120	default y
121	help
122	  Say Y here to trace all commands, including TX frames and IO
123	  accesses, sent to the device. If you say yes, iwlwifi will
124	  register with the ftrace framework for event tracing and dump
125	  all this information to the ringbuffer, you may need to
126	  increase the ringbuffer size. See the ftrace documentation
127	  for more information.
128
129	  When tracing is not enabled, this option still has some
130	  (though rather small) overhead.
131
132	  If unsure, say Y so we can help you better when problems
133	  occur.
134endmenu
135
136endif
137
138config IWLMEI
139	tristate "Intel Management Engine communication over WLAN"
140	depends on INTEL_MEI
141	depends on PM
142	depends on CFG80211
143	depends on BROKEN
144	help
145	  Enables the iwlmei kernel module.
146
147	  CSME stands for Converged Security and Management Engine. It is a CPU
148	  on the chipset and runs a dedicated firmware. AMT (Active Management
149	  Technology) is one of the applications that run on that CPU. AMT
150	  allows to control the platform remotely.
151
152	  This kernel module allows to communicate with the Intel Management
153	  Engine over Wifi. This is supported starting from Tiger Lake
154	  platforms and has been tested on 9260 devices only.
155	  If AMT is configured not to use the wireless device, this module is
156	  harmless (and useless).
157	  Enabling this option on a platform that has a different device and
158	  has Wireless enabled on AMT can prevent WiFi from working correctly.
159
160	  For more information see
161	  <https://software.intel.com/en-us/manageability/>
162
163	  If unsure, say N.
164