At present the pre CAC is done based on original SAP's BW,
but usually the original SAP is on 2G and BW <= 40Mhz. The
requirement from user is to have higher BW on 5G. Hence, select
higher BW supported by SAP phymode to do pre CAC and move 2G
SAP to 5G pre CAC channel when pre CAC done successfully.
Also set the default MAX bw pre CAC to 80Mhz based on current user
request.
Change-Id: I3115da8eb649238da50b223c2587db96125ec813
CRs-Fixed: 2984084
This reverts the change to do the memset of SW2TCL desc consumed by
HW to zero.
Change-Id: Ie56207cf483643f6e294df23f5445ca853a75d51
CRs-Fixed: 2984818
In wlansap_get_csa_chanwidth_from_phymode(), update the
channel width correctly incase when SAP starts on 2.4GHz
and channel switch happens on 5GHz channel with BW 80 MHz.
Currently host modify the BW according to the original BW
20MHz is incorrect, it should be changed to 80MHz.
Update the BW correctly, it should not be limited to orig BW.
Change-Id: I9baf89d89eeb6407c7cda931b332bced38cc2154
CRs-Fixed: 2974565
Station sends the BA and upgrades to the next possible BA window
size upon receiving all frames successfully from the current
window. Some IOT APs go out of sync from BA window size of the
station when AP fails to receive the BA sent from station. AP
transmits the frames again with previous window sequence number
and won't be ack'ed by station hardware as BA window has already
moved ahead. So, station deletes the upgraded BA and tries
to fallback.
Ideally, AP is supposed to consider the fact that "the previous
window transmission was successful when station upgrades to next
window size". But some APs take little longer time to
recover/upgrade to next window size. Don't delete the BA
immediately and have some tolerance(3 seconds) as the previous
negotiated BA just got deleted.
Change-Id: I6b277223f02dac521316cec20bd5d958785cc2e9
CRs-Fixed: 2970714
Add DP reason code support for sending DELBA request,
so protocol layer can make decisions for special cases.
Change-Id: I4eeba3513820a98a15682190e40a06ce178d9441
CRs-Fixed: 2983544
There is a time involved between the smmu fault initiated
and the eventual system panic. In this time there is a
possibility of the nbuf history being overwritten losing
the information on the nbuf which might has actually caused
the SMMU fault.
Set the ssmu state and dont track the nbuf's when the smmu
fault is detected.
Change-Id: Ia9f422861cbb7bde1b498d8a88967616be99bb6e
CRs-Fixed: 2960063
Trigger SSR if pe session already exist for vdev, i.e vdev is
not in init state during connect req.
Also Add SSR if roam command timeout.
Change-Id: I83be76215f5c4daca2429a2528f825baabed92e3
CRs-Fixed: 2982362
After DUT STA connected 40M AP, if AP switch to 20M, DUT need update probe
rsp IE of current AP and send to upper layer, but ht info tlv length in IE
is changed by mistake for wrong ht info struct type is used, then android
can't parse ht info and following RSN IE, can't get encryption method
correctly.
Change-Id: I84eab86514601f1efb1fda792148e611c290925d
CRs-Fixed: 2977335
Currently sending IPA STA_CONNECT evt after setting the flag
is_authenticated to true, which causes STA_CONNECT evt not sent
always, this is a propagation error as its implementation is
different than mainline, so moving it ahead.
Change-Id: I5073bae0a1a6048de2b6da44cda92c0a7259d98a
CRs-Fixed: 2983093
In monitor mode in case of restart failure,
event WLAN_VDEV_SM_EV_START_REQ_FAIL is used to move the vdev SM
to init state. But this event will not be handled in
WLAN_VDEV_SS_START_RESTART_PROGRESS and thus the vdev stop/down
won't be sent for the vdev.
Use event WLAN_VDEV_SM_EV_RESTART_REQ_FAIL for restart failure
to send vdev stop/down.
Change-Id: I2db459136955b8dc2213c0251284a08a8f57aa57
CRs-Fixed: 2964875
Avoid connect try to next candidate after 20 sec and thus
try to limit max connecttime to 30 sec to avoid active command
timeout.
Change-Id: I039b3d99eb77cf0148d104053c3bac86d03ad204
CRs-Fixed: 2982358
Initiate WLAN_VDEV_SM_EV_START for connect only in INIT state
as if its not in init state the VDEV SM is not cleaned up, which
needs to be debugged.
Sending WLAN_VDEV_SM_EV_START can cause pe session leak if the
event is handled by VDEV SM and return success. This can eventually
lead to all the pe session in used state.
Change-Id: I8245a7985bb08b04008b4f833f9474947c1bf57b
CRs-Fixed: 2982070
Add sanity check for RRM global channel list to avoid
possible NULL-Pointer issue.
Change-Id: Icfbf5282304a549a0dc92889f83cb1a31dde15b2
CRs-Fixed: 2972194
Currently, rssi of rx data packet is not received as part of rx_tlv_hdr.
To mitigate this limitation, fill the average rx rssi received from
firmware in wmi smart monitor event which is stored in pkt_capture's
vdev_priv structure.
Change-Id: I3a1b7b766979816d6b17f05edc1c25d503edec1d
CRs-Fixed: 2958109
Add function to populate the rx average rssi received from target in
pkt_capture vdev_priv structure. The rx average rssi is received in
wmi smart monitor event.
Change-Id: I9206669b418a2245bb8d53920040fddea77ce06c
CRs-Fixed: 2969242
Register handler for wmi smart monitor eventid in packet capture
mode in lithium. Currently, wmi smart monitor event provides
average rssi of last ten received data packets.
Change-Id: Ieeea5cbef328b04f139f54e7a42d52a3cf25824b
CRs-Fixed: 2969245
Currently GRO flush is being skipped if bus bandwidth level
is low this is resulting in rx packets to be in queue for more
time and affecting over all RTT value.
To avoid this for non legacy clients GRO flush is not being skipped
even at low throughput level.
Change-Id: I5ce64ee2bd5f332cf4db38116b1bbf400220269b
CRs-Fixed: 2978843
When vdev down flag is set, rx thread needs to flush the
pending frames in a fixed timeout value. Overall scheduler
timeout value is 10s, fixed timeout for each thread is 4s,
so if more than two threads timeout happens, scheduler timeout
may happen and lead to crash. Change to use adaptive timeout
for each thread to make overall threads wait time less than 10s.
Change-Id: If8acdaf1cac9d776e15d3020c8152101eae74a0c
CRs-Fixed: 2973947
Currently, host prints only one peer info instead of
all peer info as part of oem_ss initiated broadcast
SAP TWT get_status command.
Add a support to print all peer info if oem_ss sends
broadcast SAP TWT get_status command.
Change-Id: I0a617f655b7a5486582cb47a4602b30514ffae88
CRs-Fixed: 2970487
Currently ini based tx aggr support disabled due to firmware
incompatibility.
This change is to enable ini based tx aggr support based
on firmware capability.
Change-Id: Id5d7197f18fafd926de889f9b69ca2be90497fd2
CRs-Fixed: 2859709
This reverts commit I9e49ad5218f913f116cf4472f768f572740f14df
since ini based tx aggregation is configured based on firmware
capability.
Change-Id: I54541cd282eda6606e75fa347989624a0e0fef01
CRs-Fixed: 2963280
In case of WTC_BTM roam trigger reason, if FW reports rssi
threshold for 5G and 6G AP via wmi_roam_trigger_reason,
Host should print it in kmsg.
If wtc_candi_rssi_ext_present is set (1), It means fw
reports 5g and 6g candidate rssi (new firmware case).
If wtc_candi_rssi_ext_present is clear (0), It means fw
doesn’t report 5g and 6g candidate rssi (old firmware case).
Host use flag "wtc_candi_rssi_ext_present" to keep backward
compatibility.
Change-Id: Idbaac2e9d470525641c152b024b8786d262e600c
CRs-Fixed: 2965025
In WEP connection, IV values used for consecutive packets
could be random and need not be monotonically increasing
or consecutive in case of fragments. This could result in
incorrect drop of fragments.
Fix is to not do PN check in case of WEP security.
Change-Id: I8bfe16f3bf68752f4279b3fae1cf485a3abc1af7
CRs-Fixed: 2977416
There is potential risk when starting CFR and resume happens at same
time. Wake lock is added to CFR component, and this change enables
wake lock for enhanced CFR.
Change-Id: I1ebe8c11fad66b66adcad0b551756abf2c010cde
CRs-Fixed: 2977699
Based on new requirement create a sysfs file dump_in_progress,
this file has read and write functionalities for a bool variable,
if the value in this file is set to 1 cnss_diag will trigger
DEBUG_DUMP cmd to wpa_supplicant_8_lib through wpa_ctrl socket.
After log copy completion cnss_diag will reset sysfs node to 0.
Change-Id: I93f612d3caf4ef6ad5db98bc531ab091e96c7817
CRs-Fixed: 2971373
