Rename wlan_cm_ese_populate_addtional_ies() to fix misspelling in the
name: addtional ==> additional
Change-Id: I3a5528d09804628cc665ee882ced3af2581b0f34
CRs-Fixed: 3281750
Fill the number of links that need to be forced inactive
when the force mode is MLO_LINK_FORCE_MODE_INACTIVE_NUM.
Change-Id: Ifd24ba213a9cf011535bfd3662dd83e5b584aa51
CRs-Fixed: 3277465
In lim_tx_mgmt_frame, if opmode is QDF_NAN_DISC_MODE, pointer session
is NULL. Pointer session is used later in LFR2 code.
The LFR2 code in lim_tx_mgmt_frame should be called when the opmode is
not QDF_NAN_DISC_MODE.
Change-Id: If9848782473b7b38c3a0cbec30d7d870aceb619f
CRs-Fixed: 3287894
Currently host does not consider band capability when it decides
supported wifi standard info. This results in incorrect supported
wifi standard info. For example if dot11 mode ini is set to auto
and 6 GHz is disabled from band capability and if host does not
support 11BE, in this case if host does not consider band
capability it reports supported wifi standard as wifi 6E, but
ideally it should not report wifi 6E as it wifi 6E mandates
6 GHz support.
To address above issue, consider band capability as well to
decide supported wifi standard.
Change-Id: Iae7804a73d8ba36ec855fdc4c00ca3106e43b350
CRs-Fixed: 3282169
Currently, in host drivers, compilation fails for some TWT API when
definition is not available for either of 11AX feature flag
(WLAN_FEATURE_11AX) or TWT feature flag (WLAN_SUPPORT_TWT).
Add support for the dummy TWT API to resolve the compilation error
when 11AX and TWT feature flags and are not defined.
Change-Id: I3fa96393d5cdac9e5222b3978108601e1a651143
CRs-Fixed: 3292454
dp_stats is of type struct dp_tx_rx_stats, but memory is allocated of type
struct hdd_tx_rx_stats. Both structs are of different size and
sizeof(struct hdd_tx_rx_stats) is lesser than sizeof(struct dp_tx_rx_stats)
which is causing access out of bounds.
Fix this issue by allocating memory of size matching its type.
Change-Id: Iccc04c38fb64d65f3483ae9b128dc316e7036ec5
CRs-Fixed: 3290287
Currently in case STA is up on 5 GHz channel,
2 GHz band is preferred for P2P CLI and SAP when
concurrency priority is throughput and power
instead of SCC channel.
Fix is to prefer SCC channel in case of
throughput an power instead of moving
to another mac.
Change-Id: I0a2eef10e92f277b38e6ae80961e8d6e27047169
CRs-Fixed: 3289767
Add new ini "enable_responder_secure_ltf_support" for R-STA
secure LTF support. Enable this ini for R-STA to advertise
secure LTF support in extended capabilities & RSNXE.
Change-Id: I474b06c52c47b5a54dc827031bf9ff7c0d2f7d05
CRs-Fixed: 3283083
Currently when Zeta feature is enabled, there is a
race condition between WiFi DISABLE from TZ/CND, and
WiFi ON from UI.
Whenever TZ/CND sends WiFi DISABLE, driver will initiate
idle_psoc_shutdown, and sets is_wlan_disabled flag in the
hdd context, which will block WiFi from turning on.
But if the driver receives WiFi ON from UI before setting
the flag, it leads to a race condition.
To avoid this issue, set the is_wlan_disabled flag before
initiating idle_psoc_shutdown, and reset it if idle shutdown
isn't successful.
Change-Id: Ie643b02ebd492f637cc910be00d8226a843c2884
CRs-Fixed: 3282845
Clean up useless legacy code wma_roam_auth_offload_event_handler.
It is replaced by target_if_cm_roam_auth_offload_event already.
Change-Id: I473d20f70c00c7d0e4c390a19b4ec6fdf9c0268b
CRs-Fixed: 3290006
Send MLO Roam config to target, including:
support_link_num: Configure max number of link mlo connection supports.
support_link_band: Configure the band bitmap of mlo connection supports
Bit 0: 2.4 GHz band support if 1
Bit 1: 5 GHz band support if 1
Bit 2: 6 GHz band support if 1
Change-Id: Id59fc93cc271266ff794702d997ffc5113de5bc1
CRs-Fixed: 3273012
Issue is: Invalid pointer access (unmapped address) in
gpLimCnfWaitTimer deactivate due to invalid assoc Id.
With change If62a6082f073ce4f7084a48a4f8e60407ddfeec8,
Host directly updates the sta_ds->assocId as
assoc id given by ap in assoc request. As this is
related to the way host store the peer in internal
data structure, In case if value of assoc id coming
from AP is greater than the array size of CNF_WAIT
timer.
Fixes are:
1. Remove changes introduced by the commit:
If62a6082f073ce4f7084a48a4f8e60407ddfeec8
2. Update Association Identifier from pe_session
for STA.
Change-Id: Ib0c9facb70c459b7ca62454f2e92b33f51443f01
CRs-Fixed: 3274812
At present Pre CAC work queue callback pre_cac_handle_failure
doesn't release the vdev ref count. And the pre_cac_handle_radar_ind
doesn't take ref count before schedule work pre_cac_work.
To fix inconsistency by using psoc as work queue callback parameter
and get pre CAC vdev id from psoc context.
Change-Id: I65339ca9f3ac4b91faf31090978337d041320f99
CRs-Fixed: 3288125
fill the MCS rates for TDLS off channel, update wma pouplate
to fill peer assoc mcs values in peer assoc command.
Change-Id: I16073a51a8949093872f7a421e0ad01648b63e92
CRs-Fixed: 3275175
After roam sync is recevied the phymode will be updated for bss peer.
For MLO roaming use link address and channel to find the bss peer and
update the phymode.
Change-Id: Ic181fdb73ceeb8dfb980a4121a7569b12d3361dd
CRs-Fixed: 3280059
Rename __lim_is_defered_msg_for_radar() to
__lim_is_deferred_msg_for_radar() to fix misspelling: defered ==>
deferred. In additional, fix other instances of that misspelling in
code comments.
Change-Id: I333fcb7a728bc9defce9e55e39153898f9b5035a
CRs-Fixed: 3281814
Update the prealloc size for RXDMA_BUF and REO_DST
rings using the ini values which have been configured.
Change-Id: Idc53bf8626017dd234767da65e131557f3a5600d
CRs-Fixed: 3283991
Currently there is no support to advertise SAR
version to user space for new QCA vendor command
QCA_NL80211_VENDOR_SUBCMD_GET_SAR_CAPABILITY.
Add support for the new vendor command to send
SAR version to user space.
Change-Id: I6890da31d2e60c1a363fd8fbc8d0d0bddd29ef74
CRs-Fixed: 3273690
To enable the below 2 features in FW:
1. IDLE roam scan
2. Roam triggered due to high channel utilization
in the currently connected channel
Currently, if "roam_triggers" bitmap is set for above
features, Host indicates FW that "IDLE roam scan"
and "roam trigger due to BSS load" features are
enabled irrespective of corresponding INI
'enable_idle_roam' and 'enable_bss_load_roam_trigger'
respectively.
Consider the value of corresponding INI also while
sending enable indication to FW.
Change-Id: I0d59e0a32df4aa95850f12a99bae439fea40acf5
CRs-Fixed: 3281952
Rename mac_register_sesssion_open_close_cb() to fix misspelled word
"sesssion" in the name.
Change-Id: Ica569a3997c12baad2c61fed40e2f6721a833630
CRs-Fixed: 3278113
For associating to a ML capable AP, driver will use link address.
During dynamic MAC address update the link address in VDEV MLME
is not updated, so leading to sending the auth request with
older link address.
Update the link address as well during dynamic MAC address update.
Copy MLD address in the hdd_adapter only for ML adapter type.
Change-Id: I534e075bb26efeb3c035652cddc5d8d665604089
CRs-Fixed: 3287245
Host driver sends RSO stop request to firmware as part of
disconnect and waits for RSO stop response. It pauses the
disconnection and resumes once RSO stop response is received
from the firmware.
But cm_lock is not taken when disconnection is resumed from RSO
stop response path. This causes synchronization issues with
north bound thread which issued the disconnection.
Acquire cm_lock by using cm_sm_deliver_event() API to avoid
this issue.
Disconnect initiator thread and scheduler thread are
synchronized with this change. So, no need to set the RSO
state to STOPPED before sending RSO stop command to
firmware. So the change: I4d43508bdee2b33caba28579939fffdebfab121d
can be reverted.
Change-Id: Id29cd992ecd1bd75cb1b32eebb9e46ca5dcc728d
CRs-Fixed: 3285154
Correct Min, Max and Default value for INI
RoamRSSI_Trigger to avoid Out of range error while
cfg ini item parsing in host.
RoamRSSI_Trigger_min 50
RoamRSSI_Trigger_max 100
RoamRSSI_Trigger_default 75
Change-Id: Ifd4f049987c797ca43a865cefbc2d2517560f105
CRs-Fixed: 3283130
Currently host uses starting address of below structure
to compare between SSID coming via association request
(here SSID name is "12") and SSID at which SAP is up
(here SAP SSID name is "13").
typedef struct sSirMacSSid {
uint8_t length;
uint8_t ssId[WLAN_SSID_MAX_LEN +1];
} qdf_packed tSirMacSSid;
SSID First Bytes Second Bytes Third Bytes
“12” Length of SSID = 2 1 2
“13” Length of SSID = 2 1 3
lim_cmp_ssid(), calls qdf_mem_cmp(), to compare 2 bytes
of memory starting from pointer to session_entry->ssId
above structure. In the above case content of the First
bytes and Second bytes are the same, so qdf_mem_cmp()
returns true to caller API even though both SSID is not
exactly the same. This results in even though SAP's SSID
name is "13", the host allows the processing of an
association request from a client with destination SSID
name is "12" and with the same MAC address, which is not
expected.
To exact Comparision between SSID, lim_cmp_ssid() should
call qdf_mem_cmp() with starting address of pointer to SSID
array present in above structure.
Change-Id: I9879fe09d383b04ec8ab5ad738d1d8efa8fb0f7e
CRs-Fixed: 3282602
