Refine p2p connection status update, use API p2p_status_update
to update p2p connection status.
Change-Id: Ica1b1cfc56c09e10664cd9130d5bfacc83e2763a
CRs-Fixed: 3076205
In cm_roam_btm_query_event, token and reason code is not
copied to wlan_log_record.
Add changes to copy token and reason code to wlan_log_record
in cm_roam_trigger_info_event.
Change-Id: I7e90017070edd61215eaea77fd3af22ae9465d83
CRs-Fixed: 3071239
If p2p go+go concurrency exist and g_enable_go_force_scc ini sets
to 2(liberal mode) then 1st p2p go channel should move to 2nd
p2p go channel after set key. Again, when user initiates CSA to
one p2p go then the force SCC doesn't happen to other p2p go.
But the expectation is all p2p go should move to same channel
which is initiated by user.
As part of fix, move all p2p go to same channel when user
initiates.
Change-Id: I1664e5a7d545d29c32b94e8e4831c71a9cc0ae23
CRs-Fixed: 3064245
In case of STA+SAP, ingress qdisc filters are getting
configured on both STA and SAP interface which is
causing GRO to be disabled.
Check for ingress qdisc to enable/disable GRO only in
case of stanalone STA and not do this in case of
concurrency.
Change-Id: I3542930c7b14d72e267378dd4687ee9721eed4ed
CRs-Fixed: 3062195
Validity timer value is printed wrongly in logcat
logs for BTM request event. This is because the value
is filled from disassociation timer instead of the
validity timer field.
Also the neighbor report related prints are seen
only if the roam msg info TLV is present, which is
not correct.
Fill validity timer in BTM Request event and print the
neighbor report related prints on receiving 11kv
TLV.
Change-Id: I59606f27b0836ea567fed561bbe19f600377d3ed
CRs-Fixed: 3069855
Currently driver QCA_WLAN_VENDOR_ATTR_DIAG_BTM_TARGET_BSSID uses
instead of QCA_WLAN_VENDOR_ATTR_DIAG_BTM_TARGET_BSSID attribute
in the BTM response event. This causes the target bssid field to
be missed in BTM response print.
The WTC BTM response event is not queued when reason code is
non-zero.
Use QCA_WLAN_VENDOR_ATTR_DIAG_BTM_TARGET_BSSID attribute.
And queue the WTC btm response event.
Change-Id: Id713bfeda20c43148e95630f5c6e925b80418ca3
CRs-Fixed: 3071242
FW sends lower band end frequency filter in service ready
ext2 event.
Frequency Info for every supported mode gets updated in
wma_update_hw_mode_list when service ready ext evt is
received.
Although, FW sends lower band end frequency filter in
service ready ext2 event.
So, update SBS Frequency Info when Service ready ext2 evt is
received.
Change-Id: Iefe1e601bffaba877979e7ce42a32763b61293c2
CRs-Fixed: 3073649
At present, we select max possible band width for SAP in concurrent of
STA+SAP. If STA is working on 160Mhz, the SAP will follow the same
BW as STA. But customer doesn't want to move SAP to 160Mhz
if the original SAP starting BW is 80Mhz since the 160Mhz SAP will
have DFS limitations.
This change avoid 160Mhz selection for 5G SAP force SCC if
1. the channel switch request is not user initiated and
2. the original BW setting is not 160Mhz
Change-Id: I25a7c2ba6679eab8e3884e5b2332d7ed163de12e
CRs-Fixed: 3068284
If BTM/Neighbor report is sent indvidually by firmware, then the
prints are not seen in kmsg, as the driver drops the event if
roam trigger/scan stats is not present.
To avoid this, parse the BTM TLV if roam trigger/scan info is
not present.
Change-Id: I1a9f197ed66a080d7b5b5d7fd3a82aac8d1d708a
CRs-Fixed: 3062768
Support to deliver below mlme event to SON:
MLME_EVENT_VDEV_STATE,
MLME_EVENT_INST_RSSI,
MLME_EVENT_TX_PWR_CHANGE.
Change-Id: I0535d80cea155f5b94abecfa609d34940e57cdd7
CRs-Fixed: 3054810
Add the support for the feature of Full Power Down while
in low power mode.
For this feature, it need to power down wlan chip when
suspend, and power up wlan chip when resume, so need to
change to call wlan driver shutdown and then power off the
wlan chip instead of calling wlan driver suspend when do
suspend, and changing to do power on wlan chip, download
wlan firmware, and calling wlan driver reinit instead of
calling wlan driver resume when do resume.
Change-Id: I293647175c151da0fd6628345f98ea65c83b1bb3
CRs-Fixed: 3061366
In some scenario, it is required to receive every ARP/NS packet even
it is not to solicit address itself. So add this vendor attribute
configuration to enable/disable ARP/NS offload on fly.
On some platform, if target suspend to WoW mode, APF filter will drop
such ARP/NS packet in the front, so prevent runtime suspend happen
if disable ARP/NS offload. System suspend still allow in consideration
of potential power impact.
It only support on STA/P2P-Client mode device, and this configure is
optional, while default behavior is ARP/NS offload enable. It will
restore to default behavior if interface being closed.
Change-Id: Icd49e230024bc1ce51519cd9fafee9bc9f79f382
CRs-Fixed: 3058494
Add ini support for tx_retry_multiplier and send
tx_retry_multiplier to fw as PDEV_STATS_TX_XRETRY_EXT
pdev param, so that fw can multiply the counter by the
percentage provided by user.
Change-Id: Ie2f06dc3aaa4a161a451b68abd085cc1537eb468
CRs-Fixed: 3066799
In cm_roam_trigger_info_event, fw_timestamp is not copied to
wlan_log_record.
Add changes to copy fw_timestamp to wlan_log_record in
cm_roam_trigger_info_event.
Change-Id: I8ec7796b656d716e6ab3b7613be0c1332d5c9fa0
CRs-Fixed: 3068843
Add self bss roam check in roam invoke cmd handler,
If ini enable_self_bss_roam is 0, don't permit to roam
to current connected bss, just keep current connection.
Change-Id: I7fe724e26d15bcc008957829e4e3384c60b58773
CRs-Fixed: 3069587
This change sends the new wow event in the bitmap to FW only
when the roam stats suspend mode attribute is enabled from the
user space.
Also, the new wow reason is added to wake up the host while
sending the roam event stats.
Change-Id: Iaefb229929e8791870f33bf787487f7c20daf218
CRs-Fixed: 3050830
In cm_roam_scan_info_event, qdf_mem_copy is performed with
different sizes.
Fix is to assign frequency values instead of mem copy.
Change-Id: Ie7dc4eaf4d7c0b65100edd77d7c2306e53e2ea9b
CRs-Fixed: 3065698
This change gathers the roam event stats from the FW.
New vendor event is used to fill in the vendor attributes
whenever the roam stats are received from Firmware.
Change-Id: I9a2ddef62d26b0b68897891788733df452ac1ceb
CRs-Fixed: 3036518
Add new vendor command to enable the roam events stats from the
driver/FW in both resume and suspend mode.
New roam param is introduced to indicate the FW to enable/disable
the roam stats using the new roam set command.
Change-Id: I6d04f0946e6735613a4cf3d4361bf31052314fa0
CRs-Fixed: 3036518
Update the concurrency policy for STA mode.
For an upcoming STA connection:
1. Disallow the 2nd STA connection if multiple STA connections are
not allowed.
2. Allow the secondary MLO link when primary link is connected.
3. Disallow ML STA when ML STA/SAP is present.
4. Disallow the 3rd STA.
5. Allow for the other cases.
Change-Id: I70c41177b7a3a9aa9cbac0aaced08c6eafca2b6d
CRs-Fixed: 3012577
Cleanup WMA HWMODE and WMA HWMODE List
as the same functionality is already taken
care by policy manager
Change-Id: I5dc1342422e70737111f882013ed3a6351a85336
CRs-Fixed: 3064739
Modify policy_mgr_is_concurrency_allowed() to support
SBS concurrencies as well. For this, the following
sub functions are modified/added:
policy_mgr_allow_same_mac_diff_freq(): Check whether
different Frequencies are allowed on same MAC
policy_mgr_allow_same_mac_same_freq(): check whether
given frequency is allowed for same mac
Modify policy_mgr_allow_new_home_channel() to consider
Frequency Range of Mac instead of Operational Frequency
Band.
policy_mgr_allow_sap_go_concurrency() is also modified
to consider frequency range.
Change policy_mgr_is_5g_channel_allowed() and
policy_mgr_is_6g_channel_allowed() to allow STA on SBS
channel if SAP/Go on DFS Channel and no other active
2.4 Ghz connection.
Change-Id: Ifcd001d70e4705b33f1b7e2e3f6c296e0545eeeb
CRs-Fixed: 3052778
INI item enable_dynamic_pcie_gen_speed_switch is no longer. Hence,
delete all uses cases of it.
Change-Id: I1082620c4354bda48ebc54aae7e72e5a81c4aa94
CRs-Fixed: 3068122
If STA + STA concurrency is in DBS then irrespective of
primary interface configuration, DUT should meet below
expectations:
1. Roaming should get enabled on both the STAs interfaces.
2. Host should ensure that roaming bands are restricted to
maintain only DBS
Change-Id: Ib28cb232650893e46da0dd8e7d47d3876546a1a1
CRs-Fixed: 3056820
Update policy mgr sbs lowerband end freq
with the value received in FW Rx service ready
event.
Change-Id: I1664876765dcd5217ffce62ec81ba59b36bbaf21
CRs-Fixed: 3065151
This change fixed compilation issue when defined macro
WLAN_FEATURE_CONNECTIVITY_LOGGING but no WLAN_FEATURE_ROAM_OFFLOAD.
Change-Id: I78f58c2bcfffb66ddf9390a8d724821faa90563c
CRs-Fixed: 3066954
This change fixed compilation issue about the 64-bit division in
sdxlemur - a 32-bit architecture, which is not defined
"__aeabi_uldivmod" for the 32-bit architecture.
Change-Id: Ief75e7903fe301f5641fa4f734dc8129a7501b7e
CRs-Fixed: 3067887
For the WTC BTM roam trigger, BTM response is not printed.
So print the BTM response logs for WTC BTM frame also.
Change-Id: I679697ec08a42a862c251175261162bc95206d03
CRs-Fixed: 3062727
Along with 11BE feature macro, check for Kernel 11be macro to avoid
compilation issues when kernel doesn't support 11be.
Change-Id: I9fb84b6263cbdca4cde93e3a581acdbfe0fe2b34
CRs-Fixed: 3066175
The RF test mode cfg item is kept as 1 by default and no action is required
during init if it is set.
Change-Id: Ieb561fb81f77470c45df46ee2319ff51c05df742
CRs-Fixed: 3056554
Firmware might send NDP peer indication/NDP responder response
while NDI deletion is in progress. Currently, NDP peer entry
gets added though vdev is moved to DOWN state and cleanup is
in progress. This leads to stale peer entry on that NDI vdev
and doesn't allow vdev delete when IFF_DOWN comes, as a peer
is present.
Check the vdev state before creating peer for NDP and skip
peer creation if NDI vdev is not in UP state(which indicates
that the vdev down is happening).
Also, don't process the NDP confirm if NDP peer is not created.
Change-Id: I73e79cc33b1a294e3f4a4a6e2f371033862c5709
CRs-Fixed: 3061756
While logging, scoring info freq param is not updated.
Fix is to add freq info in the log record sent to supplicant.
Change-Id: Id3c0d154e245376f494970c99589db0c3d37f7ac
CRs-Fixed: 3065693
When ADDROAMSCANFREQUENCIES is received, the specific channel
list is not flushed in the driver. This causes the static
channel list to be sent to firmware.
Flush the specific channel list when the ADDROAMSCANFREQUENCIES
command is received.
Change-Id: Id0422f9c5a4b10530fecc309a78cedf9adbc43af
CRs-Fixed: 3063734
Add Ini to Disable/Enable SBS.
Also, if INI is set then only set
the fw mode config bit corresponding
to SBS.
Change-Id: I839990dcd9bd2daf3df2c64abe5fa74a99c73051
CRs-Fixed: 3065084
In STA+STA case, if SSR happens, driver will clear the
no_of_active_sessions = 0 at the beginning of wlan shutdown
by policy_mgr_clear_concurrent_session_count.
In the shutdown process, one STA will be disconnected and
in the setting PCL of second STA, the no_of_active_sessions
will be decreased to 255 from 0
in policy_mgr_store_and_del_conn_info.
Fix by move the policy_mgr_clear_concurrent_session_count
to policy mgr enable/disable.
Change-Id: I70bcc60fe3030db71376a626d6f9625fe299417d
CRs-Fixed: 3063772
When a sta is being steered, sending a deauth may interrupt the
association/EAPOL handshake on the new BSS.
Do not kickout sta if it is being steered.
Change-Id: I15dd26bca27699087cdb790de8cb95281dade385
CRs-Fixed: 3042990
Check the existing two connection are in below comibation or not
GO + GO
GO + GC
GC + GC
GO + STA
GC + STA
If the existing two connection are in above combination and third
connection comes as GO or GC or STA then check whether firmware
supports p2p-p2p concurrency or not.
if firmware supports p2p-p2p concurrency and third connection is
GO or GC or STA then only allow the third connection as GO or GC
or STA otherwise do not allow third connection as GO or GC or STA
with above combination.
Change-Id: I0c2408232e84438dc5dd8d104b75fdee126aa31f
CRs-Fixed: 3043845
2 threads blocked to wait channel_switch_complete_evt for SAP channel
switch is already in progress, qdf_event_set only woke up 1st thread
later, 2nd thread still kept blocked with hold net_dev for debug id
NET_DEV_HOLD_COUNTRY_CHANGE_UPDATE_SAP, leak happened.
Change-Id: Iad296f68aeaefe5a6b88ad6bea95cc377b2ae515
CRs-Fixed: 3061960
Based on the new NCHO requirement, allow ADDROAMSCANFREQUENCIES to add
roam scan frequencies irrespective of the roam scan control value.
Change-Id: I5742f6d590e3ec51bfb294610ede05b1935a4790
CRs-Fixed: 3046763
Host sends the EXT CAP IE based on the capability
coming from the supplicant in join request. But, after
roaming the cached join request will be freed. Therefore,
after roaming few capabilities sent by the userspace are
not saved and therefore lost in reassoc request.
Save the EXT CAP IE from the join request in the VDEV
and use the cached capability for sending Ext cap IE.
Change-Id: I71947388b4c6e9e56a5832557416d9b462de70e2
CRs-Fixed: 3038496
There is frequent output when get unexpected vendor specific action
frame. So, add this change and reduce the log level.
Change-Id: I9d832546a4436bdf7dd25cb00a7de5cce1295b31
CRs-Fixed: 3060750
Currently, target_if forwards the blacklist event to upper layers
even if there is no AP info present. This event can be dropped in
target_if to avoid accessing unallocated memory.
Change-Id: Icfaabb0a8e3304882979ffde7f5cd27fd4c8a067
CRs-Fixed: 3057424
Add support to send beacon miss disconnection logging event.
Fix the diag attribute end marker in the event table.
Change-Id: I11fc8859af383b69bcba42654fb3a2bc597fef83
CRs-Fixed: 3056266
Currently WMI_DBGLOG_TIME_STAMP_SYNC_CMDID command sent
every 1 sec causes RTPM collapse and inturn has power
impact. So to avoid this enable time of the day synchronization
only after connection/roaming.
Send WMI_DBGLOG_TIME_STAMP_SYNC_CMDID as part of RSO
start command.
Change-Id: Iee3cefe1318a6e5507a43cefb9666cc2a439fe06
CRs-Fixed: 3060762
