Since TDLS and STA share a common netdev interface,
when STA connection is made in 11a, 11b, 11g mode,
netdev parameters such as TSO/checksum are disabled.
If TDLS connection is formed over this Station,
TSO remains disabled as STA netdev is used.
This might result in loss of throughput when TDLS
connection is made with 11n, 11ac, 11ax dot11mode and
with wider bandwidth TDLS, this loss is more prominent.
Hence, overwrite the netdev params to enable TSO when
TDLS connection is formed in 11ax, 11ac, 11n mode if
the station is in 11a, 11b, 11g mode.
Also, disable the TSO params when TDLS tearsdown when
STA is in 11a, 11b, 11g mode.
Change-Id: I80deaef40d70030211e75a63e1339b1407627b52
CRs-Fixed: 3245258
Currently in hdd_init_channel_avoidance api we are proceeding for
malloc without checking unsafe channel count.
To address this issue add check before calling qdf_mem_malloc api
to check if unsafe channel count is greater than 0, otherwise
return from the function.
Change-Id: I4d54a6aa97a141be06695d2455fb5d6aff8db082
CRs-Fixed: 3273502
With change in design, now in 2.4 GHz band TDLS
BW should always follow Station bandwidth. So,
No need to set widerband bit if TDLS connection
is created on 2.4 GHz Band and offchannel is not
enabled.
Change-Id: I19d69c57a042feb72e50059bdca28c7a4263adb8
CRs-Fixed: 3269866
Currently, in the function hdd_cache_ll_iface_stats,
the adapter is dereferenced without validating it.
To avoid possible null-pointer dereference, add a check
to validate the adapter.
Change-Id: I6a905db2ada90243f178237bab41fd975789b8c1
CRs-Fixed: 3273525
Prensently for initial scan and roam passive scan dwell time,
the same ini CFG_PASSIVE_MAX_CHANNEL_TIME is used. This will
cause initial scan to have the roam passive scan value.
Decouple passive scan and roam passive scan ini parameter by
adding new ini param for roaming
Change-Id: I4b37c8faa26c971f173e8c8179e505ea4c69c27e
CRs-Fixed: 3268789
Del_key is called by supplicant for every key index and driver
logs error if mac address is NULL. This adds 18 ms delay due
to the kmsg error print and causes supplicant to delay
processing the EAPOL-1 frame, which leads to AP retrying
EAPOL-1 frame.
So change error log level in __wlan_hdd_cfg80211_del_key to
debug and remove redundant vdev id validation which is already
done in the caller.
Change-Id: I2dffd480a8ac2021b4683c5c5583ef9483935b5d
CRs-Fixed: 3260194
Reset the HE capability data buffer after the 5 GHz HE capabilities
are configured to FW to fix the malformed data in 2.4 GHz HE
capability data.
Change-Id: I8147ffdae1990cf1997650f0790a27ccbb6ff1fe
CRs-Fixed: 3253505
Remove the MLO IE sent in connect request association request
data to avoid duplication.
Change-Id: Icccf378c05cd9509dfbb42d68a9859c9a0bb315a
CRs-Fixed: 3259650
When NAN is not supported on some target(disabled through ini
param gEnableNanSupport), there is no use of reserving vdev for
it in firmware though firmware advertises wmi_service_nan. Indicate
firmware that host is going to take care of the NAN vdev creation.
Host can use the vdev either for NAN or other operations
on need basis.
Change-Id: Iec106ceb80b80f03017a77036727b148845b64d5
CRs-Fixed: 3267080
Sometimes country change happened when driver is loading stage.
wlan_hdd_validate_context will return EAGAIN in such case and
cause country change work aborted. Reschedule country change work
in EAGAIN case so that country change work can be done.
Change-Id: I83efb6def92a2f3c2710df02f85383ccb20e89d2
CRs-Fixed: 3252694
Avoid code duplication by using common definitions
i.e use enum wlan_ml_linfo_subelementid.
Change-Id: Ib8ce8f5e84abe7a8d60ebc220610dcc60483bf81
CRs-Fixed: 3270765
In case of failure policy_mgr_is_restart_sap_required
returns without releasing the lock. This leads to lock leak.
Fix is to release the lock before return in case of failure.
Change-Id: I032a6902de1bd0c8f87b660aac98a2fb08dd3f10
CRs-Fixed: 3269538
Reinitialize mon_register_event before wait_for_completion
to make sure that it waits for fresh completion.
"done" variable in struct completion increments in
complete() API and decrements in wait_for_completion() API.
In wait_for_completion() API, if "done" value is 0 then
it will wait for the completion else it will continue without
waiting.
If reinitialization is not done, there is a possibility that
wait_for_completion() may continue without waiting.
Change-Id: I780103f551938438f27a11b006cc7c3e6edc6820
CRs-Fixed: 3251876
Currently, cap_mask contains the bitmap to check if any bits
other than SAE_H2E, SAE_PK, SECURE_LTF, SECURE_RTT,
PROT_RANGE_NEGOTIOATION are set in RSNXE capabilities.
But if the cap length is non-zero, the cap_mask wrongly indicates
that some bit is set in the capabilities other than the above
mentioned features as first 4-bits are used for length.
Skip validating the first 4-bits as these are reserved for
cap length.
Change-Id: I3736479e7c580425f8d340cb5bd815836c54d5ce
CRs-Fixed: 3270051
Multiple instances of the misspelling "recevied" are present, so
replace them with the correct spelling "received."
Change-Id: Ie0421bc472d5c25f1fbcc5e8c9333e0283a6e129
CRs-Fixed: 3271103
For non-dbs HW, per INI g_sta_sap_scc_on_dfs_chan description, standalone
SAP should be allowed to do channel switch when sta_sap_scc_on_dfs_chnl
is 0 or 2.
Change-Id: I380791debed79d4de6d468afe0c8956bf6f11ddb
CRs-Fixed: 3265470
Currently, HE cap uses the final cap derived from 2 GHz and
5 GHz specific HE caps, then the value of rx_pream_puncturing
in HE cap may not be expected when 5 GHz is used.
To resolve this issue, set rx_pream_puncturing if 5 GHz band
is used.
Change-Id: I81cb960271dff5007606a10cab8e9c78cbae58fb
CRs-Fixed: 3267557
Add os if layer for CoAP(Constrained Application Protocol)
component. It provides interfaces to parse netlink messages
for vendor command QCA_NL80211_VENDOR_SUBCMD_COAP_OFFLOAD
and take action accordingly, including enable/disable offload
reply/periodic transmitting for CoAP messages, and fetching
CoAP messages those cached during offload processing.
Change-Id: Ibbf9baf3802d305f9989e024ce764a6071b1fc6b
CRs-Fixed: 3254541
On some projects, LFR3 roaming is not supported due to
limitation of FW memory, thus, add support for WPA3 LFR2
roaming.
Change-Id: I80888049a243c0d37e08377d89a6aa44e75a8850
CRs-Fixed: 2973554
Currently, it DUT only supports one link,
lim_gen_link_specific_probe_rsp returns error. It causes
one link connection failure.
To resolve this issue, return success if DUT only supports
one link.
Change-Id: I9fcad7e82865ff6a4424ca74ea60f68e3a59ea21
CRs-Fixed: 3270226
If policy_mgr_is_concurrency_allowed is false, don't set
weighed_valid_list = WEIGHT_OF_NON_PCL_CHANNELS. Keep
WEIGHT_OF_DISALLOWED_CHANNELS for them so that the interface
won't start on disallowed channel. And in P2P+P2P or SAP+P2P
case strictly follow PCL weightage for second P2P interface.
Change-Id: I005e680e796269d3cd847b5df460506813d0d033
CRs-Fixed: 3265478
Send the failure response if the association response generation
is failed for link vdev to release the connect request command.
Change-Id: I0d05347c61cfd8fea90b23c3de6f0fb1ba7752d4
CRs-Fixed: 3253510
If the acs scan is optimized based on last scan ageout time,
it can lead to either skip ACS scan fully or scan partial
ACS frequency list. If ACS scan is skipped or partially
done, use a scan filter based on last scan ageout time to
retrieve the scan entries for ACS algorithm.
Change-Id: Id1d3a3d4364163686f92c380e9f6d6dada033ff5
CRs-Fixed: 3239389
In GO+STA+SAP concurrency, if GO is MCC with STA, the new SAP
will not be allowed in same MAC. FW doesn't support MCC in same
MAC for 3 or more vdevs. Move GO to other band to avoid SAP
starting failed.
Change-Id: Ia19abd1b11f7416797af3e975ab8ffde9037c11f
CRs-Fixed: 3262185
Currently wma_find_vdev_id_by_addr searches for the mac address of the
vdev there are some function which pass the mld address to this
utility api which is currently returning error.
Search with mld address alo in wma_find_vdev_id_by_addr.
Change-Id: I34ef8486a406cbaadbe95e5cb493bc5b0c8d8b0c
CRs-Fixed: 3270810
For 2.4 GHz band, if AP switches its BW from 40 MHz to 20 MHz, it
changes its beacon respectivily with ch_width 20 MHz without STA
disconnection.
This will result in TDLS remaining on 40 MHz and not follwoing APs BW
on 2.4 GHz.
Better Teardown the link here and with traffic going on between peers
the tdls connection will again be restablished with the new BW
Change-Id: I7f7b3cdc7937b2d4b78df46ca970fae22efc2ead
CRs-Fixed: 3243624
If SAP+P2P GO SCC on 2.4 GHz, the new STA interface will be
allowed connect to AP on 2.4 GHz SCC channel of SAP/GO or
5/6 GHz band AP. And do same for 5 GHz band.
For 3rd SAP/P2P GO coming up, try to force SCC to
existing same band SAP/GO home channel if any, to avoid the
concurrency check failure.
Change-Id: I363e9c8307ac4cfa70d6d00bc0d01a545c3eca26
CRs-Fixed: 3249205
