FISA update may come when target in suspend state, then
UMAC force wake may return failure and lead to system timeout
crash. Change is used to defer the update when resume happens.
Change-Id: I8d3082355f780d11fd5047d67f916f0a7dd0c6e8
CRs-Fixed: 3325498
With WLAN_FEATURE_NAN=n and kernel version > 4.9.0 , wiphy_register()
returns failure and throws below warning:
WARNING: CPU: 1 PID: 8 at net/wireless/core.c:641
wiphy_register+0x5ac/0x944
With above config, NL80211_IFTYPE_NAN is not advertised to
wiphy->interface_modes. But NL80211_IFTYPE_NAN is advertised
to wiphy->iface_combinations. Hence the failure and warning are seen.
Fix is to advertise NAN iface_combinations only when NAN feature
flag and kernel version are met.
Change-Id: Iaceea699939df919c17dc81a1195f7dea1543982
CRs-Fixed: 3329527
If ml sta is not "connected" state, no need to do link state handling.
After disconnected, target will clear the force active/inactive state
and host will remove the connection entry finally.
After roaming done, active/inactive will be re-calculated.
Change-Id: Ic9ba3e3ef704b3dcdd8185e9b0864a9cbac000c7
CRs-Fixed: 3322063
With 11be mlo, the number of open station interfaces is 3.
Modify the check in policy manager api for the same.
CRs-Fixed: 3320739
Change-Id: I89166ebdf1559cde6f77f5a5c535e5f2e81eefc5
Currently, the driver has VHT rate table for MCS
indices ranging from 0 to 9, but FW supports VHT rates
for MCS 10 and 11 as well. So, update the VHT rate table
accordingly.
Change-Id: Iecb55d664f6dbb4a10eb98d75cf942af4833ca45
CRs-Fixed: 3325194
Currently, roaming is disabled with requestor "RSO_CONNECT_START"
on the STA when concurrent P2P-client is connected .
It's re-enabled once the P2P-client is disconnected but with
requestor RSO_INVALID_REQUESTOR. Roaming module still doesn't
re-enable roaming as it expects roam-enable command from the
requestors(i.e. RSO_CONNECT_START in this case) which disabled
roaming.
Pass right requestor to re-enable roaming.
Change-Id: Icb3deeed788ca248391b4b84288229aea2bdb8c2
CRs-Fixed: 3330219
Currently in function hdd_get_station_info, it does not malloc the
NLA_HDRLEN for each attribute, it causes no enough buffer to put
the data.
Since in that function, it combines lots of info for the station,
define WLAN_STATS_INFO_LEN to malloc enough buffer.
Change-Id: I31deccb329c5b14abc97e30ee75de9452f0e06e0
CRs-Fixed: 3325629
Currently host driver indicates frame pcap logging feature as
supported by default to fw.
Host driver does not support this feature as of now, so indicate
this feature as not supported to fw in feature set capability info.
Change-Id: I5a6f4d83cca1b5b92d8a9159b68349534b112d92
CRs-Fixed: 3329222
For MLO STA+SAP case, mlo link maybe in inactive state after
connected and the hw mode maybe not updated, check MCC/SCC by
policy_mgr_are_2_freq_on_same_mac may not match MCC/SCC state
after the link is activated by target later. So to check frequency
match or not to decide SAP do force SCC or not if MLO STA 2 links
are present.
Change-Id: I614e6879cf4f9614b979fc3c78f87b76fc6c7c16
CRs-Fixed: 3313043
Currently sme_switch_channel set new_ch_width as phy_ch_width, while
wma_csa_offload_handler set new_ch_width as raw bit in wide bandwidth
channel switch IE.
Clean up the code. Define new_ch_width in csa_offload_params as
phy_ch_width.
Change-Id: Iadecc7693bf4ffd9f9562405ef18ea9d25d45c9e
CRs-Fixed: 3324762
Whenvever WiFi is disconnected, link layer stats are cleared
by wlan_hdd_clear_link_layer_stats(). In the current driver
implementation the statsClearReqMask is set clear IFACE_AC and
IFACE_ALL_PEER only. This results in driver reporting incorrect
contention stats, even though WiFi is disconnected.
To resolve this issue, update statsClearReqMask to clear
IFACE_CONTENTION stats as well.
Change-Id: I1e07df91823db1db70f73075982e551f4b8a85c7
CRs-Fixed: 3323943
If existing STA+STA is MLO STA, the current HW mode is not
reliable because the STA link maybe inactive. HW mode may
change if MLO STA becomes active.
Add special handling to this case by checking MAC frequency
range to decide DBS or SBS.
Change-Id: I4d3728965d2f687805535abb0716bb1b58e1c51d
CRs-Fixed: 3328517
In concurrency case: GO on 5180 MHz, SAP on 5765 MHz,
MLO STA vdev 0 5180 MHz, MLO STA vdev 1 2462 MHz.
When the MLO STA is up and driver does force SCC on
SAP, the get PCL is failed because the GO vdev,
MLO STA vdev 0 and vdev 1 are all non-SBS channels
between each other. Driver doesn't handle the case in
policy_mgr_get_index_for_ml_sta_sap_sbs if current
hw mode is SBS. This case can happen the mlo sta link
vdev is inactive after get connected.
To fix it add new API:
policy_mgr_get_index_for_ml_sta_sap_hwmode_sbs to
handle it. It will return the correct PCL index
to avoid 3 home channels on same mac.
Change-Id: Ia16f8a391b34fc15287a93590b2c119d58250e20
CRs-Fixed: 3326358
Remove WMI_PDEV_PARAM_SET_CMD_OBSS_PD_THRESHOLD which is sent to
initialize the hardware registers. The initialization of hardware
registers is done as part of WMI_VDEV_PARAM_SET_CMD_OBSS_PD_THRESHOLD
Change-Id: I272fbd6723836efb9864cb78bdaf3e0eacf45554
CRs-Fixed: 3329913
Change the default driver log trace level for HAL
to INFO. This is to disable logging the debug logs
from HAL module to the driver logs.
Also fix the way in which DP module default log
level is being set.
Change-Id: I8b068f31dcb733bf7714b6e7234f01f3ce180edf
CRs-Fixed: 3319410
In case of ML SAP, userspace needs assoc resp IE to get all
the ML link info.
So, Add support to save assoc_resp ie pointer in peer common object
which will send to userspace.
Change-Id: If19857ecce62092b1aa4e7fef17c09e819822f5f
CRs-Fixed: 3325938
In case of bandwidth is 80/160 MHz, use ccfs0 value from VHT
or HE ops and if bandwidth is 320 MHz, use ccfs1 value from
EHT ops. Thus, ccfs0 value in EHT op is redundant and needs
to be ignored.
Change-Id: Ia8f988ac28349be7bce47388d9f8b844fa52a90e
CRs-Fixed: 3305667
Currently, SR enable can be set even if sta is not connected
to AP due to which success is returned to userspace but command
is not sent to FW.
Fix is to not to entertain any SR operation if station is not
connected or connected AP is not supporting SR.
Change-Id: Ie46e5f4db12a1ecf8eea44847a97355f26163ed8
CRs-Fixed: 3321577
Add sr_enable_mode ini to check SR(Spatial Reuse)
can be enabled for non-STA mode or not. If SR
can't be enabled for non-STA mode and concurrency
is not allowed then don't allow any SR operation.
Change-Id: I876882c48c54f216bc1d0efa4dccce63f2a2e63c
CRs-Fixed: 3311374
Currently, Host considers HW power limit received from
FW via vdev start response along with other parameters
like regulatory channel power, AP constraint, and TPE
IE for TPC power calculation.
FW calculates this power for default LPI power mode.
If Host associates with an SP AP, it still uses this
LPI-specific value and could result in capping tx
power to a lower value than expected if this HW power
limit ends up being the limiting factor in Host.
Thus, ignore this field altogether while calculating
TPC power and Hal Phy will apply other limits
once they receive set tpc WMI from Host.
Note- HW power limit is still valid for tx power
calculation in the case of legacy Host (old WMI
vdev_set_param with WMI_VDEV_PARAM_TX_PWRLIMIT
param id).
Change-Id: Ia3af651a765c5440f3a37c6d1144ef08882e4938
CRs-Fixed: 3312165
Add a fallback mechanism if a 6 GHz AP does not advertise
TPE IE.
1) Currently for the 6 GHz band, is_psd_power is obtained
from AP's TPE IE. But if it is not present, obtain it
from the regulatory channel list.
2) If is_psd_power is false, current logic calculates
center frequencies for BW > 20 MHz. These center
frequencies are then passed as input to fetch EIRP power
which is incorrect and results in zero which makes overall
tx power as zero. Thus, use operating frequency itself to
obtain EIRP power.
3) Despite these checks, if regulatory power results in
zero due to invalid frequency or other inputs, assign this
field to the regulatory channel power of the operating
frequency.
Change-Id: I70ae301de21cb8d696fee3c3f9d5fd30d1b53a8b
CRs-Fixed: 3327259
STA_ENTRY_TDLS_PEER is defined under feature flag FEATURE_WLAN_TDLS.
With FEATURE_WLAN_TDLS=n, compiler throws use of undeclared identifier
'STA_ENTRY_TDLS_PEER'.
Hence fix the error in wma_he.c:1276 introduced in change
I16073a51a8949093872f7a421e0ad01648b63e92.
Change-Id: I0038dad70147b5c4ded2abad34baf50c8bc32f83
CRs-Fixed: 3275175
EHT IEs such as EHT caps and EHT ops are missing from
the beacon data buffer. Add a new API to append these
IEs to the buffer. Also, add support in the driver to
populate wiphy EHT caps with SU Tx beamform parameters.
Change-Id: Ia7640602410ba6802eb017bf763707f84e6e7c83
CRs-Fixed: 3325336
Correct bad misspelling of IE decriptor_element to
descriptor_element in frame parser file and subsequently
dot11f source and header files and the parser API file.
Change-Id: I0aedb44ffdb9a407721bfe5f30ce23cd40efcbf1
CRs-Fixed: 3314908
Update CFG_DISCONNECT_ROAM_TRIGGER_MIN_RSSI INI min, max
and default values under macro
Change-Id: I9973a032d16c5d8aedb4ad77833b9124de719e86
CRs-Fixed: 3314826
Parse new nudge attribute to support flexible TWT.
This attribute is optional and will override wake
duration attribute if provided.
Change-Id: I16bbd5e4c78e5471cdccad4ebe43049d4f85e829
CRs-Fixed: 3265813
policy_mgr_get_nondfs_preferred_channel() return a non-DFS channel
with channel bw 20 MHz, but if the original SAP bw is 160 MHz and
channel is on 5 GHz, it always has DFS bonding channel.
So reduce channel bw if detect the bonding channel is DFS channel.
It can make STA connect to 5 GHz ref-AP even SAP is on 5 GHz channel
with 160 MHz bw.
Change-Id: I842d9dfb1070b900e52841b4ec5372af8550ad8e
CRs-Fixed: 3318696
Consider the bw passed by supplicant/hostapd for P2P Go
starting on 6 GHz band.
Only Overwrite the bw when the P2P Go interface is coming
up on 5 GHz band (80 MHz) and for 2.4 GHz band (based on channel
bonding).
Change-Id: I628bd1e4008f811e6f8d72508a33527bbe8cf762
CRs-Fixed: 3324343
