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
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
Add support to configure HE +HTC support in HE caps and HE OM
control transmission.
Change-Id: Ic3ad5952198472ecda79471a37ff527dfdbcdbf0
CRs-Fixed: 2359376
1) 'ssdp' in t_wma_handle structure is not used anymore,
remove this redundant field.
2) ucfg_pmo_set_sta_mod_dtim and ucfg_pmo_get_sta_mod_dtim
should have been accessing 'sta_mod_dtim' instead of
'sta_dynamic_dtim' in struct pmo_psoc_cfg.
Change-Id: Iedd7bed1c9f637a819f97b6d8c687b784739dd62
CRs-Fixed: 2415087
It won't free the nbuffer when tx mgmt frame and don't found session,
then cause memory leak. So free memory to avoid memory leak.
Change-Id: I4e6c2fcdcbf9fa549887602eeaeee3126edc1ef5
CRs-Fixed: 2400974
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmPrevTrafficCnt to be compliant.
Change-Id: Icf8e455e81145c5319f943308c078db7ca01c8b5
CRs-Fixed: 2414525
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmInactivityTime to be compliant.
Change-Id: Iceffbf91bba02635d0174fa25db3d0401e450146
CRs-Fixed: 2414524
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmInactivityTimer to be compliant.
Change-Id: I23b0d28adaa95cc6f127c6309788366f259a4a88
CRs-Fixed: 2414523
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmAcUapsdDirection to be compliant.
Change-Id: Ifd22bf0a1ae974ff1425d88e15a1702ddad3d2b7
CRs-Fixed: 2414522
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmAcUapsdSuspensionInterval to be compliant.
Change-Id: Ia309e77f9ee13251b84dc4f825a19d0222dfd648
CRs-Fixed: 2414521
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmAcUapsdServiceInterval to be compliant.
Change-Id: I93337f46663e40521b6baf467abcff59cca98cc8
CRs-Fixed: 2414520
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmAcIsUapsdEnabled to be compliant.
Change-Id: I4f109c7806881b358886e24e7876aac7c24918fb
CRs-Fixed: 2414519
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmAcTspecInfo to be compliant.
Change-Id: I707b0351effc4a6d5d2554a283c519c89b0f0b42
CRs-Fixed: 2414518
The curTxMpduCnt member of tDphHashNode is initialized but is
otherwise never modified or read. Since it is obsolete, remove it.
Change-Id: I73c5c296b38dc5a8794862c5314fdf5f63e6c0d4
CRs-Fixed: 2414744
The lim_send_probe_rsp_mgmt_frame() parameters n_staid and keepalive
are not actually used, so remove them.
Change-Id: Iccaecb9abe336b0cad943b2c77944ff555d523cd
CRs-Fixed: 2414655
The fragSize member of tDphHashNode is initialized but is otherwise
never modified or read. Since it is obsolete, remove it.
Change-Id: I7cdf9c62b25d14f9d74ac5144def2a6d4e69ca7c
CRs-Fixed: 2414654
The encPolicy member of tDphHashNode is initialized but is otherwise
never modified or read. Since it is obsolete, remove it, along with
the macros that define the values that it formerly used.
Change-Id: If6698217b6c7d10840f0776c77678861be026c2b
CRs-Fixed: 2414653
The tDphHashNode is no longer part of an ABI, so using rsvd1 to
preserve bit positions is no longer required, so remove it.
Change-Id: Iea1a757d30f93a31fc1b0a315cae512bfce95d31
CRs-Fixed: 2414649
The defaultKey and defaultKeyId members of tDphHashNode are unused, so
remove them.
Change-Id: I8ec6c73d55de3b3873797c5b0cbb0fa1e6eafe74
CRs-Fixed: 2414647
The baPolicyFlag in tDphHashNode is initialized to 0xFF in several
places, but is otherwise never modified or read. Since the member is
obsolete, remove it.
Change-Id: I57acb5d878aa3e37c654f27d79517a8c9bcf7742
CRs-Fixed: 2414646
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmAcUapsdInfoValid to be compliant.
Change-Id: I54960d0902f3a1396d9c24a315d2438c584a323b
CRs-Fixed: 2414517
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmAcTspecValid to be compliant.
Change-Id: I36d38c2774ab062e81d52581fee3d7c3bebad9a5
CRs-Fixed: 2414516
The Linux Coding Style frowns upon mixed-case names
so rename HDD identifier wmmAcAccessAllowed
to be compliant.
Change-Id: I83ea1945057ce281f5862feefaf4e09cbd2fe948
CRs-Fixed: 2414515
The Linux Coding Style frowns upon mixed-case names
so rename HDD identifier wmmAcAccessGranted
to be compliant.
Change-Id: I23521ad0a8184e25b4e5ed88899b11bb2e56318c
CRs-Fixed: 2414514
The Linux Coding Style frowns upon mixed-case names
so rename HDD identifier wmmAcAccessFailed
to be compliant.
Change-Id: I149b1d76a799b87e8fbf6814280c760b0a9e0d26
CRs-Fixed: 2414513
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmAcAccessPending to be compliant.
Change-Id: I1daf7585bc82f11887502b4664c6735570f52939
CRs-Fixed: 2414512
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmAcAccessNeeded to be compliant.
Change-Id: I45a447f0a0a464d543a9da06cf0da1e9854a32f1
CRs-Fixed: 2414511
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmAcAccessRequired to be compliant.
Change-Id: I7492d6e53624d741a87a3ebbb414d48139d0c8f0
CRs-Fixed: 2414510
Add Diag log support for logging cold boot calibration
data sent by firmware via cold boot cal wmi event.
Change-Id: I932fd5f87667498b77ee13ca5b3ce08d6001cdf0
CRs-Fixed: 2413450
If Firmware supports NDI DBS mode, driver can support NDI
concurrency along with NAN and STA type connecitons. Use
Policy Manager API's to add support for these concurrencies.
Add policy mgr related changes to support NDI concurrencies.
Change-Id: If272be34606c0897d0b145c602b4bc2ba4462cb0
CRs-Fixed: 2384549
NAN Datapath implementation allows more than one concurrent
NDI's to be active at the same time. But this isn't supported
if there is a higher priority incoming connection such as
STA. Add modules that check for unsupported NDI concurrency
and initiates termination of all NDP's on it.
Add modules that check and disable unsupported NDI concurrency.
Change-Id: I6ad9afbfc41beda1d1c8f31bf58a8ea70027f5ca
CRs-Fixed: 2407215
Currently pno related parameters are getting populated in
wiphy before scan related inis are initialized, and because
of this, wiphy is not getting initialized correctly as ini
scan_support_enabled for pno is not initialized yet.
Wiphy is registered once FW ready event is received,
ideally wiphy parameters which are dependadnt on FW
capabilities or cfg items should be configured once
FW ready event is received.
To resolve this issue, update sched scan related parameter
initialization after FW ready event is received.
Change-Id: Ib0cdb145caa5a0b9911365750fbfd38dc954dee3
CRs-fixed: 2400148
Currently the driver populates the he caps value from the mlme cfg
which is the max MCS set that the driver supports in 11ax , i.e
for 2x2 mode, but dont consider the session nss, i.e the intersection
of AP, and the self capability, hence the assoc req is sent with
2x2 MCS rates in HE caps.
Fix is to change the MCS set according to the nss value of the
session.
Change-Id: I0ca4778eeafc3469611109b420e4dd58cc8e8ae8
CRs-Fixed: 2410721
If DBS 2x2 mode is supported, to operate in 2.4Ghz the driver needs to
be in DBS mode before vdev start/restart is sent on 2.4Ghz channel.
In scenareo with gWlanMccToSccSwitchMode 4, when AP is in 5Ghz and
STA connect to any other channel in 5ghz, it force AP to switch to 2.4 Ghz
channel. Thus AP sends vdev restart without sending the HW mode change
to firmware.
Fix is to set HW mode before the AP start channel switch.
Change-Id: I2a1c176d5f3ed8cc2f62dc24c72959db1afbaae3
CRs-Fixed: 2414034
To address kernel control flow integrity (CFI) issues related to type
mismatch, correct the input argument type for sme_ser_cmd_callback().
Change-Id: I3f0b5df70163eca9282d2b1c2a48203448e4f0a6
CRs-Fixed: 2402977
Allow driver to send RSO command irrespective of value of INI
FastRoamingEnabled.
FastRoamEnabled has nothing to do with LFR enable or disable.
Change-Id: Ice5e653b249f988a49d18ed56c9be53d4436bf56
CRs-Fixed: 2385045
The current implementaton of iw_get_oem_data_cap() has a few issues:
- It has identifiers with mixed-case and Hungarian notation
- It performs an unnecessary data copy
So refine the function to address these issues.
Change-Id: I3d445ea4024e072d66c3d59e8773d0ad72eb6178
CRs-Fixed: 2413669
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmContextList to be compliant.
Change-Id: Ia48fa11624e9f4413871a1f443503cbacc86f09f
CRs-Fixed: 2412983
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmAcStatus to be compliant.
Change-Id: I64f0ea0d96253594ddc62cce9601e331470f0d1a
CRs-Fixed: 2412982
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmQosConnection to be compliant.
Change-Id: Ib23c8cca8d1adbb2fcc86686477aa5470e1b761e
CRs-Fixed: 2412981
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier wmmQap to be compliant.
Change-Id: I016bb2ce37d46ad246b89c95b0062a7f4a22f880
CRs-Fixed: 2412980
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier qosConnection to be compliant.
Change-Id: Iff26d78b773411d7addb86100f9607d7dc414a14
CRs-Fixed: 2412979
