Currently UMAC_CRYPTO_OBJS are added to OBJS when
CONFIG_CRYPTO_COMPONENT is enabled. An upcoming change requires that
assignments to OBJS be unconditional, so relocate the condition to
wrap the assignment of UMAC_CRYPTO_OBJS.
Change-Id: I28ca48d6876307814ce440a3fe53cb8f8df1d42f
CRs-Fixed: 2867906
Currently DP_OBJS are added to OBJS when CONFIG_LITHIUM is enabled.
An upcoming change requires that assignments to OBJS be unconditional.
Fortunately most of the assignments to DP_OBJS are already protected
by this feature. Update the logic so that all of the assignments are
protected, and remove the condition from the OBJS assignment.
Change-Id: Icc7d015831d8940bf1d91335be1439a70965801f
CRs-Fixed: 2867900
Currently hal_rx_flow.o is assigned to DP_OBJS, but since this is a
HAL file, change the assignment to HAL_OBJS.
Change-Id: Ie7c56300d3dd60b52305b5b3c7ace58c6e8cdb57
CRs-Fixed: 2867882
Currently TXRX3.0_OBJS are added to the OBJS aggregation only when
CONFIG_WLAN_FEATURE_DP_RX_THREADS is enabled. However only one of the
object files, dp_rx_thread.o, should be controlled by that feature.
Update the logic to conditionally add dp_rx_thread.o to TXRX3.0_OBJS,
to encapsulate all TXRX3.0_OBJS assignments within CONFIG_LITHIUM,
and unconditionally add TXRX3.0_OBJS to OBJS.
Change-Id: I6ceeafeab43a960277a1870daff5566288199ada
CRs-Fixed: 2867843
There are currently two different places where ol_txrx_event.o is
added to the final target object list. As part of ongoing Makefile
cleanup consolidate these to a single location.
Change-Id: Id342ae771830f5fd4d65c6c5523c36f1e50bc941
CRs-Fixed: 2867841
FISA debug macro is leading to unnecessary additional functional calls,
to avoid this cleaning up macro and pointing to nop when disabled.
Change-Id: I21ebd64f61e2c31736d55e2d17f588dbddbc15c7
CRs-Fixed: 2869361
Fisa flow entry napi id is initialized to invalid value,
which will cause out of bound access during fisa flush by vdev id.
Fix this by validating array index before access.
Change-Id: Ic7b1b1448194b75777f9dc392043275235caa7f7
CRs-Fixed: 2873033
1) Enable skb accounting for rm/gno/hst on auto platforms.
2) Remove an unused ini item name.
Change-Id: I19f8b70a409bb6485eea08fdbdf3a8e34839bf59
CRs-Fixed: 2872544
Reduce stack frame size of wlan_update_bss_with_fils_data()
by allocating dynamic memory to fils indication.
Change-Id: I799100558b4192f4be2eaa1fb4f9508a2cb73e66
CRs-Fixed: 2868544
According to new requirement, when SAP manadatory channel list
enabled (gWlanMccToSccSwitchMode = 4,
gEnableSAPManadatoryChanList=1), the SAP will only be started on
PSC and VLP channels on 6Ghz band. Add all 6GHz PSC & VLP channels
to SAP mandatory list.
Change-Id: I00514c0af9c1cc07460120c928ced652aa2e8d4e
CRs-Fixed: 2870590
To make it generic, rename the flag QCA_WIFI_NAPIER_EMULATION
as QCA_WIFI_EMULATION.
Change-Id: I8e654262a38a7a701a5a34e2bbd5394c8985c65a
CRs-Fixed: 2871313
Currently when TWT commands are sent to firmware, the host driver
doesn't acquire wake lock. So the wlan can got to wow mode before
receiving the TWT command response and the response will get
dropped since host is in wow mode.
To avoid this make the TWT events as wakeable so firmware can
wake up host if host is suspended.
Change-Id: I2750049f9173de564e24114731d3fdd8ec8d6d86
CRs-Fixed: 2869865
When the TPE IE comes to driver, there could be information for both
local and regulatory. Add an INI for preference in the case that both
sets are present.
Change-Id: I4b37123569f422863fc805063974c65878a9baea
CRs-fixed: 2854774
Refactor WLAN_FEATURE_PKT_CAPTURE_LITHIUM to WLAN_FEATURE_PKT_CAPTURE_V2
and refactor pkt_capture_get_pktcap_mode_lithium to
pkt_capture_get_pktcap_mode_v2 to remove hardware name from compilation
flag and function name.
Change-Id: Id12c60a47dee95a719cc39aa0803edc9582dda3b
CRs-Fixed: 2869808
Increase the default value of gInterfaceChangeWait timer from
10000 to 300000, when QCA_WIFI_NAPIER_EMULATION is enabled.
Change-Id: I8c3b7907fc2ccfcbbdb152e28a1364630c99555a
CRs-Fixed: 2871256
Add WMI service FW capability check before enabling D0 and D3
WoW for SAP and GO clients connected mode.
Change-Id: I878e4ee33807804e049bf1e8b8078d28fc1d4834
CRs-Fixed: 2869072
Zero initialization of Napi id can cause napi id zero context to flush
flow that are uninitialized. Which may cause a race condition if some
other napi context is using the uninitialized fisa flow entry during the
flow learning phase.
Change-Id: Iedca4ee112efa29c70a632c4a365e95f71e8f506
CRs-Fixed: 2864633
Host uses "oem_6g_support_disable" INI value to configure
oem_6g_support_disable of wifi pos priv psoc object. If the Reg
domain doesn't support 6Ghz band and INI "oem_6g_support_disable"
value is 0, then host enables support for 6Ghz. Thus OEM apps
supporting 6Ghz fails to get 6Ghz channel information from host.
Hence use reg domain 6Ghz support and "oem_6g_support_disable"
INI value to update oem_6g_support_disable of wifi pos priv psoc
object.
Change-Id: Id5e5b6220f3ce880da3c40aa959887ebc6bbfa7c
CRs-Fixed: 2870971
Avoid sme lock from connect/disconnect callback as the callback
already takes connection manager or sme lock.
Change-Id: Ifd5499f6756be7208d350afaae6cf637e7d69349
CRs-Fixed: 2870854
Add RSO lock and use it to send RSO commands. Also
avoid calling the cm_disconnect API while holding
SME global lock to avoid race.
Change-Id: I588a56f4c96d137d3283b2dc57274de069ecb4ab
CRs-Fixed: 2870603
Re-write TPE IE populating code. For 6ghz AP, there can be multiple
TPE IEs.The TPE IE can be of type PSD or non-psd.
Change-Id: I029d4826cbc73abb382d885260c355217b2cc6b4
CRs-Fixed: 2863009
issue step:
1 first connect with mcs_12_13 supported ap
2 switch to connect with non support mcs_12_13 ap
the linkspeed for 2nd ap will be wrong as it is leverage
1st ap's sta info in vdev_mlme_obj.
Fix is reinit mcs_12_13 in vdev_mlme_obj for each connection.
no matter if it is 11ax AP.
Change-Id: I7f6ceb2543be1df324f57183758872e6d807d8f9
CRs-Fixed: 2868617
In Dual station case, reassociate to AP which is connected on other
vdev is not supported, and will get roam invoke failure from target.
Disallow the bssid reassocaite by checking the connected vdev.
Change-Id: I4533cf8b633cec9ddebff946248dbacf8eab169d
CRs-Fixed: 2868221
Kernel maintains bss with old channel, if inform beacon before
channel switching, kernel will create new bss. And kernel will
unlink the “new” bss when process channel switch event, that could
being used by other component. Driver can avoid “new” bss creation
by removing the wlan_hdd_cfg80211_update_bss_db call before
indication the channel switch to kernel.
The kernel bss updating will happen in following beacon rx from
ap.
Change-Id: I4f1405cd3c8533bafcbd2fc0a290864cddd1e634
CRs-Fixed: 2868341