Due to PTA matser limitation, zigbee joining network success rate
is low while wlan is working. Wlan host driver need to configure
some parameters including Zigbee state and specific WLAN periods
to enhance PTA master. This mechanism is called MPTA helper.
Vendor subcommand QCA_NL80211_VENDOR_SUBCMD_MPTA_HELPER_CONFIG
is added to realize this feature. NL attributes
qca_mpta_helper_vendor_attr is used to deliver parameters from
uplayer to host driver.
Change-Id: Ic76130e4b92c88e8034f6a0c6c0447c9c6dee945
CRs-Fixed: 2407801
Due to PTA master limitation, zigbee joining network success rate
is low while wlan is working. Wlan host driver need to configure
some parameters including Zigbee state and specific WLAN period to
enhance PTA master. This mechanism is called MPTA helper. The INI
parameter gMPTAHelperEnable is used to enable/disable this feature.
Change-Id: I070c06a00ec2c405540cc40251f5cb7fec211cbd
CRs-Fixed: 2407801
The Linux Coding Style frowns upon mixed-case names and so-called
Hungarian notation, so rename HDD identifier pMFPRequired to be
compliant.
Change-Id: I4bea75c912505c856381502b225067ed5e0cdbea
CRs-Fixed: 2416636
The Linux Coding Style frowns upon mixed-case names and so-called
Hungarian notation, so rename HDD identifier pMFPCapable to be
compliant.
Change-Id: I30e04b74e0a00b5c4abd0efe9aa4e8a0002ed499
CRs-Fixed: 2416634
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier mcEncryptType to be compliant.
Change-Id: Ica46896ac8139dede8f6654acedfec04ed46e4fa
CRs-Fixed: 2416633
The Linux Coding Style frowns upon mixed-case names and so-called
Hungarian notation, so rename HDD identifier pAuthType to be
compliant.
Change-Id: I85a44aff4deca274ae3e35dbda2b05fc59c68d00
CRs-Fixed: 2416635
The Linux Coding Style frowns upon mixed-case names and so-called
Hungarian notation, so rename HDD identifier pEncryptType to be
compliant.
Change-Id: I134a791699b9d612bca35028e9f069d43c2adab6
CRs-Fixed: 2416632
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier dot11RSNIE to be compliant.
Change-Id: I07beacb9a5682df858b888cf91715f4b1c233a55
CRs-Fixed: 2416631
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier dot11WPAIE to be compliant.
Change-Id: I12298bd50ff47511dd9c88a546c66042fe828def
CRs-Fixed: 2416630
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier RSNIeLen to be compliant.
Change-Id: I3414f964d2a86915a519f74782820854705c90b6
CRs-Fixed: 2416629
The Linux Coding Style frowns upon mixed-case names and so-called
Hungarian notation, so rename HDD identifier pRsnIe to be compliant.
Change-Id: I2c2d232f4bc81e5344aa20c93c900aa629467343
CRs-Fixed: 2416628
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier rspRsnLength to be compliant.
Change-Id: Id4be0165f7d94eca3e512e62d4470288a9ae4393
CRs-Fixed: 2416627
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier rspRsnIe to be compliant.
Change-Id: Ibb64738f7e7a31bbc29191ac669de2c87c6ed42e
CRs-Fixed: 2416626
Current ACS logic sometimes selects MCC channel based on its
algo for SAP / GO which results in SAP / GO bring-up failures.
This issue is seen in below concurrency combinations:
1. SAP + SAP
2. SAP + P2P-GO
3. SAP + SAP + SAP
4. SAP + SAP + P2P-GO
So with this change driver restricts ACS scan to intersection of
PCL and ACS channel list.
This implementation will take care of existing STA + SAP case as well,
as PCL will have channels according to 1st connection being STA.
Change-Id: Ic715fb29533c20b63cffda8a82b7317904f0d291
CRs-Fixed: 2407289
IEEE802.11ai standard mandates Mobility domain IE to be
advertised in authentication frames for FT-FILS connection.
With FT-FILS akm suite connection, initial association to the
AP happens with full EAP-8021x handshake. When association to
the AP happens second time, FILS connection with auth algo 4 and
ERP keys exchange happens. During this FILS association, host
driver doesn't send MDIE in the authentication request frame.
This will result in authentication rejection with failure code:
INVALID_MDIE.
Advertise MDIE in authentication frame during FT-FILS initial
mobility domain association.
Also mark the connection as 11r connection in PE session when
the AKM suite is FT-FILS SHA-256 or FT-FILS SHA 384.
Change-Id: I4dbbd9b0ef67ef3a6eb3b8afaaaa22be260d7b3e
CRs-Fixed: 2411728
Issue analysis:
On original android Settings wifi UI, only ssid shows, several
bssid of same ssid is merged as 1 item on wifi list, user can't
select bssid but ssid.
On some special apps, all AP are shown by bssid on UI, 2 bssid
of same ssid isn't merged, show as 2 items on wifi list, once
user selects 1 item by click, bssid is set.
When connect with bssid, wpa supplicant will disable roaming,
driver will disable roaming offload scan and btm offload too.
In 11K roaming. when AP requires 1 connected STA to roam,
btm request is sent to wpa supplicant, but wpa supplicant will
send back btm response with reject reason 7:
WNM_BSS_TM_REJECT_NO_SUITABLE_CANDIDATES. AP may kickout STA DUT.
Fix:
APPs usually don't care bssid, even connect with bssid, LFR3/2
roaming should keep enabled and btm offloaded to F/W. F/W will
handle btm req and send btm resp for 11K roaming.
If one special APP wants to fix on one bssid, it can call
vendor special API to disable roaming:
QCA_NL80211_VENDOR_SUBCMD_ROAMING.
wlan_hdd_cfg80211_set_fast_roaming is called in driver to
disable LFR3/2 and disable btm offload.
AP roaming decision priority is higher than STA, even STA
disabled roaming, refuse roaming after got btm req from AP, AP
can kickout STA for load balance etc.
Change-Id: I498547be7f26392ddd110585d0475b16a4ec8d5c
CRs-Fixed: 2413272
During SSR/PDR, pktlog will be disabled as part of
hdd_features_deinit if pktlog is enabled in ini.
pktlog will remain disabled until it is manually
enabled.
In SSR case, check if pktlog is enabled in ini and
re-enable pktlog if it is enabled.
Change-Id: Idf683152cfe7ffa8c0248468f9b81f731175cb47
CRs-Fixed: 2412281
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier sapEvent to be compliant.
Change-Id: Ic5bd0709f62f99da3f3078670a0bb7774b098c83
CRs-Fixed: 2415555
Change I99a2659e2151ad285e9451b9e9cc036a199581a3 ("qcacld-3.0: Remove
legacy scan and ap protection related ini items") removed the last
usage of local variable iniConfig in wlan_hdd_cfg80211_start_bss(), so
remove it.
Change-Id: I110735dc3940150e9de5b71e0911d2fcc9a581e6
CRs-Fixed: 2415554
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier MFPRequired to be compliant.
Change-Id: Ie63644ba0f4c146cf1c29c9b086d402e7e0bd9bc
CRs-Fixed: 2415553
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier MFPCapable to be compliant.
Change-Id: Ia40d1c30915aa6ecf6e9908668d4092633079bcd
CRs-Fixed: 2415552
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier mcRSNEncryptType to be compliant.
Change-Id: I2d3b7a382ab2fdb0dc3261f92e1251405f759355
CRs-Fixed: 2415551
Currently rx_arp_resp_count stats is not updated for ARP packet
during rx in htt_rx_amsdu_rx_in_order_pop_ll as packet type is
not marked as QDF_NBUF_CB_PACKET_TYPE_ARP.
Also, track_arp_ip member of adapter is updated during NUD SET
but track_arp_ip of hdd_ctx is used inside hdd_hard_start_xmit
and hdd_rx_packet_cbk to compare arp src ip.
Update the packet type to QDF_NBUF_CB_PACKET_TYPE_ARP for ipv4 ARP
packet during htt_rx_amsdu_rx_in_order_pop_ll.
Use track_arp_ip member of adapter to compare arp src ip.
Change-Id: I58a678caa8ce4b54b583f76cfcbbb4f46443f448
CRs-Fixed: 2405335
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier RSNAuthType to be compliant.
Change-Id: If93efea4637d88a8c59f376fcc905aa4a40de574
CRs-Fixed: 2415550
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier neighborReq to be compliant.
Change-Id: I07649d9aa0ab26b69d6a1fbf7ea05ac5ce3f307f
CRs-Fixed: 2415549
Currently, driver updates lim global structure, if channel switch
parameters in the beacon/probe rsp have changed. And sends an
indication to HAL with the updated HT parameters. In case if
channel pHTInfo->primaryChannel obtained from a beacon or probe
response is invalid, driver still allows fw to switch to an
invalid channel results assert in fw.
Fix is to ignore HT channel switch parameters updates if an
invalid channel present in beacon or probe response.
Change-Id: I92d9d0917077300f719068e1e0e5cfc282010dba
CRs-Fixed: 2414170
Some malformed comments were discovered when generating
the official documentation of wlan cfg ini items.
Refine the documentation text of the following items
in one batch:
gEnableDynamicDTIM
g_sap_chanswitch_mode
gVhtChannelWidth
gDataInactivityTimeout
Change-Id: I2b1455d0ea27fd35dc0cf66316c7dc3b348ee0ac
CRs-Fixed: 2416086
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier callbackInfo to be compliant.
Change-Id: I71e41f668f0451cc482e8889fd4d751d6bb02115
CRs-Fixed: 2415548
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier tSpec to be compliant.
Change-Id: I10fd01adcc87cb2bff5d48fa349e9a355dd90683
CRs-Fixed: 2415547
In the function hdd_dns_make_name_query, the driver is performing a
validation check that includes the use of length of the received string
as an array index. As the length and string both are user controlled,
the user can send the length as zero. As the policy states that the
given attribute is NLA_BINARY, so there would be no validation check
that can ensure the correct input. Therefore in the case of a malformed
packet with null length string, it can cause a possible integer
underflow.
To avoid this vulnerability change the attribute type from NLA_BINARY to
NLA_NUL_STRING. This will cause all the checks to be performed at
validate_nla.
Change-Id: I0bb569b71a88a07745d364dad23cf1210af4212e
CRs-Fixed: 2409913
The Linux Coding Style frowns upon mixed-case names and so-called
Hungarian notation, so rename HDD identifier pRequest to be compliant.
Change-Id: I738fd83ecb00de6399f224bbfbd956dbbe5effce
CRs-Fixed: 2414998
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier offloadRequest to be compliant.
Change-Id: I8b3ee0d09cc6031a6a082a84a10173526fb46f47
CRs-Fixed: 2414997
The Linux Coding Style frowns upon mixed-case names and so-called
Hungarian notation, so rename HDD identifier pStatus to be compliant.
Change-Id: Ic4c8a4cb85a151144861ee9983e2eea5a28d7e2f
CRs-Fixed: 2414996
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier connectedBand to be compliant.
Change-Id: I6a42c38c8acdcea7a248d1b7baf7443b437985ff
CRs-Fixed: 2414995
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier currBand to be compliant.
Change-Id: I5ecc8773f985ca4558a87250446f492ec7f6b1cc
CRs-Fixed: 2414994
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier uapsdMask to be compliant.
Change-Id: I40bab07e5c7e8fd5f8be9c26732f304c0c2bfadd
CRs-Fixed: 2414993
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier queueIndex to be compliant.
Change-Id: Iaf7bc148b7559e64dcdb45ee8a7c5143467a356c
CRs-Fixed: 2414992
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier qosInfo to be compliant.
Change-Id: I6badd2c5add06830886cce3740fe15bf29dba7fb
CRs-Fixed: 2414991
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier inactivityTime to be compliant.
Change-Id: I22e52f1e916e201efb84a1fa9afffde165c1912a
CRs-Fixed: 2414990
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier currentTrafficCnt to be compliant.
Change-Id: Ic330104dc1cc74ed3f4e07534911ee5c1992f262
CRs-Fixed: 2414989