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
HE MCS map, full bandwdith UL MU-MLMO supported, partial bandwidth
UL MU-MLMO supported and partial bandwidth DL MU-MLMO are needed by
EasyMesh agent when sending AP capability report to EasyMesh
controller.
Indicate these information to SON.
Change-Id: Icbf5cb5d7a313568c6a0c1b9a3d70f1f8af4d40e
CRs-Fixed: 3278853
In default configure with sta_sap_scc_on_indoor_chan=1 and
gindoor_channel_support=0, we don't expect sap setup on indoor
channel only.
Change-Id: Ibea0eb41b20bcbdaa365bd3fa4f0a7be7b696493
CRs-Fixed: 3278223
DUT roams to 2 GHz channel 6 bw 20 MHz, OBSS parameters are not
initialized by lim_fill_ft_session. Later when DUT gets CSA event
to 2 GHz channel 1 bw 40 MHz, the OBSS scan command will send
invalid obss_width_trigger_interval with zero value to target.
Fix by initialize the OBSS parameters without check current AP's
BW.
Change-Id: I6f895371898fde292cde5a108a3b4fcd95836186
CRs-Fixed: 3287522
Two mlo sta link vdev (2+6(LPI)) are started but hw mode is SMM (one
link maybe inactive in fw).
When start SAP on 5 GHz low, driver doesn't select force SCC channel for
such case. It left the SAP channel not changed (5 GHz 5220).
Since the 6 GHz STA link is on LPI mode, SAP is not allowed on
6 GHz (policy_mgr_modify_sap_pcl_for_6G_channels). Driver needs to
consider the PCL as well to select force SCC channel. Add new API
policy_mgr_get_pref_force_scc_freq to fix it.
Change-Id: I824de7168a26955caeeaff955a232c80baa13345
CRs-Fixed: 3280704
In the current driver implementation for processing MLO LL_STATS,
host expects to receive Radio Stats as the last stats event sent
by FW in response to unified_ll_stats_get_sta command. But, if the
FW sends a dummy Radio stats event as the first stats event,
then it leads to an assertion in the host.
To avoid this issue, add logic to process MLO LL_STATS based on the
mlo_vdev_id_bitmap.
Change-Id: I83dc539c6624963cf054130ff2e3cfb3660cbaf3
CRs-Fixed: 3275406
When disconnect from wpa_supplicant and cm event from F/W happen at same
time, supplicant holds cm cm_req_lock and wait rsp of p2p cleanup roc from
scheduler thread until 2 sec timeout, sheduler thread is blocked to wait
for cm_req_lock.
When wmi peer delete of vdev0 is not sent within 1.2 sec after host send
wmi peer delete of vdev1, firmware will assert.
To fix it, don't wait rsp of p2p cleanup roc when disconnect by async way.
Change-Id: I877b7a446dfd12f621dad5049a67574359bdd322
CRs-Fixed: 3285115
Currently in packet capture, channel for data packets is updated
from pdev. We are updating channel in pdev when we receive auth
frame in mon thread. But, sometimes we are updating channel in
radiotap of M2 in pkt_capture_update_tx_status, before mon thread
process auth packet and update channel in pdev, because of
which we are updating wrong channel in M2.
So, to avoid this move update of channel from mon thread to
pkt_capture_mgmtpkt_process.
Change-Id: Icf14c4331849ad7cfdfbd7a3043e4e4dc3d33721
CRs-Fixed: 3266890
Currently hdd_regulatory_init() only updates wiphy channel info
for regdb offload case, so when in regdb non-offload case, wiphy
channel info have been updated per host driver configuration in
reg_process_master_chan_list() during wlan boot up, but wiphy
channel orig_flags isn't updated to kernel side, and kernel side
still uses original reg rules to populate wiphy channel status.
It causes the result of iw list doesn't align with driver side.
Change-Id: If667dce6e23a8f3cea0432ab11875a3c5771855d
CRs-Fixed: 3280333
Use uint8_t instead of boolean for tdls maxpeercount in
wlan_tdls_features as this will result in restricting max
supported TDLS peer count as one when more than one TDLS
peers are set.
Change-Id: I468f87e80178c0fb2e80b122f59d0dffcfa3928f
CRs-Fixed: 3284105
Currently the driver doesn't store the DBAM configuration
sent by userspace via vendor command. So, whenever SSR happens,
the DBAM configuration is also lost.
To prevent this, save the DBAM config in the hdd context
when received via vendor command and restore it after re-init.
Change-Id: I186f96505ab9856d23996a7884afff6cd5d85f2f
CRs-Fixed: 3279467
SAP fails to get RSN IE from reassoc request frame body.
Assoc request and reassoc request have different fixed parameters.
IE should be retrieved based on frame subtype.
Change-Id: I72cfc4cc28cdfeb9a35269d6c1a8c638dea87631
CRs-Fixed: 3283683
Currently the history recording for any debug purpose
is done using a contiguous memory chunk. For certain
history like tx_hw_ring, tx desc or tx completion desc
history, the amount of contiguous memory required is
very huge (order 7 or 8 allocation), which have a
higher probability of failing.
In order to mitigate the above scenario, introduce the
support for recording debug history into fragmented
chunks of memory, thereby reducing the requirement of
contiguous memory.
Change-Id: Ia725cf5d061a53009f02bddd67967360404f2f1c
CRs-Fixed: 3283778
Disable 11a support on 6 GHz band and change default rate of 6 GHz
frequency band by using WMI_PDEV_PARAM_DEFAULT_6GHZ_RATE.
Change-Id: I2db2dd54c03cf71e1b697796fa3dc58d2646a8b5
CRs-Fixed: 3251997
Link adapters are added to tail of hdd adapter list after ml adapter. When
rmmod, remove and delete all adapters from head of the list, so ml adapter
is removed before link adapters, all of it's link adapters are deleted
at same time, later link adpaters are removed from the list, user after
free lead to assert.
To fix it, when a ml adapter is deleted from hdd adapter list, need let
all it's link adapters deleted from hdd adapter list first.
Change-Id: I9a4657000e994ef64d08a6b1fa354cef0b1be6bd
CRs-Fixed: 3278312
If SAP+GO SCC on DFS channel and Radar event is detected, driver
should move out both SAP and GO to new channel. Add GO mode
check in wlansap_roam_process_dfs_chansw_update API.
Change-Id: I824553222be8a8f21ab6c4ac776a4b1e692ed3da
CRs-Fixed: 3280352
Currently, there is no interface id valid check,
Which is resulting in unnecessary Vdev NULL error
logs for interfaces for which Vdev is not created.
So to fix the excessive logging issue add a check
to validate the interface id.
Change-Id: I86b2a60c11631f5122f866a83427d4cd9b794a02
CRs-Fixed: 3283932
STA is disconnecting and set rso stop to fw, and start "RSO stop"
timer. But in middle of it, the fw csa event comes, and it clears the
"RSO stop" timer, start “RESTAT” timer.
Finally when the RSO status comes from fw, it can’t stop the rso
timer. Then the disconnecting is stuck in the state.
Fix by ignore the CSA if CM is in disconnecting or disconnected state.
Change-Id: I63f52d3a58b06ee012a05d5a4f194c32c63ab1f5
CRs-Fixed: 3281072
