[NEUS7920-218] [9610][7885][7872][7570] wlbt: Drv Changes for Wpa3
[GitHub/LineageOS/android_kernel_motorola_exynos9610.git] / net / wireless / Kconfig
1 config WIRELESS_EXT
2 bool
3
4 config WEXT_CORE
5 def_bool y
6 depends on CFG80211_WEXT || WIRELESS_EXT
7
8 config WEXT_PROC
9 def_bool y
10 depends on PROC_FS
11 depends on WEXT_CORE
12
13 config WEXT_SPY
14 bool
15
16 config WEXT_PRIV
17 bool
18
19 config CFG80211
20 tristate "cfg80211 - wireless configuration API"
21 depends on RFKILL || !RFKILL
22 ---help---
23 cfg80211 is the Linux wireless LAN (802.11) configuration API.
24 Enable this if you have a wireless device.
25
26 For more information refer to documentation on the wireless wiki:
27
28 http://wireless.kernel.org/en/developers/Documentation/cfg80211
29
30 When built as a module it will be called cfg80211.
31
32 config NL80211_TESTMODE
33 bool "nl80211 testmode command"
34 depends on CFG80211
35 help
36 The nl80211 testmode command helps implementing things like
37 factory calibration or validation tools for wireless chips.
38
39 Select this option ONLY for kernels that are specifically
40 built for such purposes.
41
42 Debugging tools that are supposed to end up in the hands of
43 users should better be implemented with debugfs.
44
45 Say N.
46
47 config CFG80211_DEVELOPER_WARNINGS
48 bool "enable developer warnings"
49 depends on CFG80211
50 default n
51 help
52 This option enables some additional warnings that help
53 cfg80211 developers and driver developers, but beware that
54 they can also trigger due to races with userspace.
55
56 For example, when a driver reports that it was disconnected
57 from the AP, but the user disconnects manually at the same
58 time, the warning might trigger spuriously due to races.
59
60 Say Y only if you are developing cfg80211 or a driver based
61 on it (or mac80211).
62
63
64 config CFG80211_CERTIFICATION_ONUS
65 bool "cfg80211 certification onus"
66 depends on CFG80211 && EXPERT
67 default n
68 ---help---
69 You should disable this option unless you are both capable
70 and willing to ensure your system will remain regulatory
71 compliant with the features available under this option.
72 Some options may still be under heavy development and
73 for whatever reason regulatory compliance has not or
74 cannot yet be verified. Regulatory verification may at
75 times only be possible until you have the final system
76 in place.
77
78 This option should only be enabled by system integrators
79 or distributions that have done work necessary to ensure
80 regulatory certification on the system with the enabled
81 features. Alternatively you can enable this option if
82 you are a wireless researcher and are working in a controlled
83 and approved environment by your local regulatory agency.
84
85 config CFG80211_REG_CELLULAR_HINTS
86 bool "cfg80211 regulatory support for cellular base station hints"
87 depends on CFG80211_CERTIFICATION_ONUS
88 ---help---
89 This option enables support for parsing regulatory hints
90 from cellular base stations. If enabled and at least one driver
91 claims support for parsing cellular base station hints the
92 regulatory core will allow and parse these regulatory hints.
93 The regulatory core will only apply these regulatory hints on
94 drivers that support this feature. You should only enable this
95 feature if you have tested and validated this feature on your
96 systems.
97
98 config CFG80211_REG_RELAX_NO_IR
99 bool "cfg80211 support for NO_IR relaxation"
100 depends on CFG80211_CERTIFICATION_ONUS
101 ---help---
102 This option enables support for relaxation of the NO_IR flag for
103 situations that certain regulatory bodies have provided clarifications
104 on how relaxation can occur. This feature has an inherent dependency on
105 userspace features which must have been properly tested and as such is
106 not enabled by default.
107
108 A relaxation feature example is allowing the operation of a P2P group
109 owner (GO) on channels marked with NO_IR if there is an additional BSS
110 interface which associated to an AP which userspace assumes or confirms
111 to be an authorized master, i.e., with radar detection support and DFS
112 capabilities. However, note that in order to not create daisy chain
113 scenarios, this relaxation is not allowed in cases where the BSS client
114 is associated to P2P GO and in addition the P2P GO instantiated on
115 a channel due to this relaxation should not allow connection from
116 non P2P clients.
117
118 The regulatory core will apply these relaxations only for drivers that
119 support this feature by declaring the appropriate channel flags and
120 capabilities in their registration flow.
121
122 config CFG80211_DEFAULT_PS
123 bool "enable powersave by default"
124 depends on CFG80211
125 default y
126 help
127 This option enables powersave mode by default.
128
129 If this causes your applications to misbehave you should fix your
130 applications instead -- they need to register their network
131 latency requirement, see Documentation/power/pm_qos_interface.txt.
132
133 config CFG80211_SLSI_SAE
134 bool "Enable SAE in Kernel"
135 depends on CFG80211
136 default y
137 help
138 This option enables sae in kernel.
139
140 This Option enables SAE in CFG.
141 This option needs to be enabled if the kernel version by default doesnt
142 support SAE.
143
144 config CFG80211_DEBUGFS
145 bool "cfg80211 DebugFS entries"
146 depends on CFG80211
147 depends on DEBUG_FS
148 ---help---
149 You can enable this if you want debugfs entries for cfg80211.
150
151 If unsure, say N.
152
153 config CFG80211_INTERNAL_REGDB
154 bool "use statically compiled regulatory rules database" if EXPERT
155 default n
156 depends on CFG80211
157 ---help---
158 This option generates an internal data structure representing
159 the wireless regulatory rules described in net/wireless/db.txt
160 and includes code to query that database. This is an alternative
161 to using CRDA for defining regulatory rules for the kernel.
162
163 Using this option requires some parsing of the db.txt at build time,
164 the parser will be upkept with the latest wireless-regdb updates but
165 older wireless-regdb formats will be ignored. The parser may later
166 be replaced to avoid issues with conflicts on versions of
167 wireless-regdb.
168
169 For details see:
170
171 http://wireless.kernel.org/en/developers/Regulatory
172
173 Most distributions have a CRDA package. So if unsure, say N.
174
175 config CFG80211_CRDA_SUPPORT
176 bool "support CRDA" if CFG80211_INTERNAL_REGDB
177 default y
178 depends on CFG80211
179 help
180 You should enable this option unless you know for sure you have no
181 need for it, for example when using internal regdb (above.)
182
183 If unsure, say Y.
184
185 config CFG80211_WEXT
186 bool "cfg80211 wireless extensions compatibility" if !CFG80211_WEXT_EXPORT
187 depends on CFG80211
188 select WEXT_CORE
189 default y if CFG80211_WEXT_EXPORT
190 help
191 Enable this option if you need old userspace for wireless
192 extensions with cfg80211-based drivers.
193
194 config CFG80211_WEXT_EXPORT
195 bool
196 depends on CFG80211
197 help
198 Drivers should select this option if they require cfg80211's
199 wext compatibility symbols to be exported.
200
201 config CFG80211_NO_BEACON_HINT
202 bool "Do not update Regulatory configuration"
203 depends on CFG80211
204 default n
205 help
206 Do not update regulatory rules based on beacon hints.
207
208 config LIB80211
209 tristate
210 default n
211 help
212 This options enables a library of common routines used
213 by IEEE802.11 wireless LAN drivers.
214
215 Drivers should select this themselves if needed.
216
217 config LIB80211_CRYPT_WEP
218 tristate
219
220 config LIB80211_CRYPT_CCMP
221 tristate
222
223 config LIB80211_CRYPT_TKIP
224 tristate
225
226 config LIB80211_DEBUG
227 bool "lib80211 debugging messages"
228 depends on LIB80211
229 default n
230 ---help---
231 You can enable this if you want verbose debugging messages
232 from lib80211.
233
234 If unsure, say N.