Proapagation from qcacld-2.0 to qcacld-3.0.
Currently pktstats are stored in static allocated memory. This
pkt stats can be accessed using
1) procEntry function
2) hal_proxy_daemon
If user access it using procEntry then read pointer is moved ahead
in static memory array because of which incomplete data goes when
queried using hal_proxy_daemon.
Fix this by maintaining the pktstats in link list. When the
request comes from hal_proxy_daemon, complete data is sent
to it from this link list
Change-Id: I09bbd03fe378b296e110ce52cc8cbeb8cf8d723d
CRs-Fixed: 958544
(cherry picked from commit c0d86fc4197383d0eb386e091cee5142a35b555a)
qcacld-2.0 to qcacld-3.0 propagation
Currently TXQ of DEFAULT_MGMT packet is using TID
HTT_TX_EXT_TID_MGMT when we inserted into Scheduler, so use
same TID when we flush it.
Change-Id: I1631b7706d1f8bf0352ceecb8836d82743526e44
CRs-Fixed: 1000968
(cherry picked from commit 9b41b24a9da6b9415ebdafb6e4574f0b03570e9e)
qcacld-2.0 to qcacld-3.0 propagation
Currently FW does not indicate wow wake up frame to host for
HL project. After the change, FW will indicate wake up frame
with HTT_T2H_MSG_TYPE_RX_OFFLOAD_DELIVER_IND htt msg and host
will handle this message to indicate to OS protocol stack.
Change-Id: I5f4446de7ec3c4ff1c1de6fd6105429e0898291c
CRs-Fixed: 956416
(cherry picked from commit b5cb00e05b1db94a2869cc5becef3d777dbd560e)
qcacld-2.0 to qcacld-3.0 propagation
In USB solution, hif_usb_remove costs ~25s after card unplugged.
Test step is simple, do p2p listen, then unplug card. Sme session
close costs 15s. When do p2p listen, scan will be issued to fw, but this
cmd is stuck in smeScanCmdActiveList which cause session close cmd
eSmeCommandDelStaSession blocked and the timeout is 15s.
This solution is that remove scan from smeScanCmdActiveList
if scan cmd pending in active list when close session.
Change-Id: I9f1af72cefe80dca056d7a23e015caa746952330
CRs-Fixed: 1068739
(cherry picked from commit b3460026a8ae119ac660b3970c9e3cc8b999656d)
qcacld-2.0 to qcacld-3.0 propagation
In a SNS case, driver receives ASSOC Req during the SAP
Stopping. The SAP stopping will issue WMI_VDEV_DOWN_CMDID
WMI command to firmware. And ASSOC req frame processing
will issue a WMI_PEER_CREATE_CMDID WMI command to firmware.
Then the firmware crash happens because firmware can't find
the necessary BSS information to create the peer. Firmware
doesn't support peer create after BSS down.
The fix is to ignore the ASSOC Req frame while the deleting
BSS is ongoing.
Change-Id: Ib517642da4fc6b4778ef1ce4e6afd92fa3edb112
CRs-Fixed: 1053809
(cherry picked from commit 2118b5d37d9294a22cff60ec5bd2b7baf4a34cae)
qcacld-2.0 to qcacld-3.0 propagation
In case of P2P device and P2P GO using seperated
interface, if P2P Device interface listen (remain on
channel) with long duration is active, P2P GO interface
vdev start command will be timeout.
In shared interface case, driver will cancel existing
P2P listen during interface type changing from P2P device
to P2P GO in __wlan_hdd_cfg80211_change_iface. There
is no such issue.
This fix is to extend the canceling logic just before P2P GO
starting to avoid the vdev start timeout in first case.
Change-Id: I5c5903bc5eded417ede670025c241daf73b96700
CRs-Fixed: 1022238
(cherry picked from commit 696a5a4e110482bcf873b6c657fe621aa2dd8b8e)
qcacld-2.0 to qcacld-3.0 propagation
If ACS failed, the __wlan_hdd_cfg80211_stop_ap
will not be called to free the ch_list.
Add new API wlan_hdd_undo_acs to do cleanup of
DO_ACS to free ch_list memory. And call the API
in hdd_deinit_adapter to fix ch_list leak issue.
CRs-Fixed: 1002207
Change-Id: If3285739f2387928a1d7578f9d14089a486a6d9e
(cherry picked from commit e55d0c20e574a63b5002650529054ace24ad7cad)
propagation from qcacld-2.0 to qcacld-3.0.
If tdls commands fail before it's really executed, the
commands in active list will not be removed and timeout.
Change-Id: Ie10458dcdef9571520b995d1879b499fe855ce2a
CRs-Fixed: 962237
qcacld-2.0 to qcacld-3.0 propagation
It's a fix for sns issue. Set DUT as sap, ref client sends assoc req
to DUT and as part of this frame processing lim does ADD_STA and posts
eWNI_SME_ASSOC_IND to sme layer. Before SME layer sends eWNI_SME_ASSOC_CNF,
DUT receives auth frame which triggers deauth. In this case lim layer
will delete ref client's related info, but wma layer doesn't get any
notification.
To fix this lim has to notify wma to do DEL_STA for that peer.
Change-Id: Id4aae51aae3fb68e752d09793ad3bce17665fc2e
CRs-Fixed: 979687
qcacld-2.0 to qcacld-3.0 propagation
Currently tx_frm_download_comp_event is used in Mcthread and destroyed
in wma_stop, when wma_stop is called, Mcthread has not exited yet.
In stress test, this event is destoryed but Mcthread is still using,
so crash occurs.
Solution is that destroy event in wma_close to avoid the case that after
destroy this event is still used.
Change-Id: I7d4e97ab261f586edfb90268544a2cda4e90a0b2
CRs-Fixed: 958906
qcacld-2.0 to qcacld-3.0 propagation
Host driver will use sap channel leakage matrix to identify whether
this channel is leakage due to radar detected in sap channel. channel
144 is missed in this table.
Change-Id: I15b8cce29da8ba5d7beef1b4e684200121a4aa61
CRs-Fixed: 945408
qcacld-2.0 to qcacld-3.0 propagation
We need to stop SAP bss and destroy the SAP
session if the channel switch failed. Otherwise,
the vdev will leak and it will cause SoftAP
start failed in following test.
Change-Id: Ieb3a2d62c8698f245f787be3c215ee4365b2e8ba
CRs-Fixed: 944741
qcacld-2.0 to qcacld-3.0 propagation
This change fixes the connection issue in ap+ap mode.
One peer may connect to the second ap while another ap
still has the connection with this peer, so the same
peer may be created twice.
Change-Id: I898ec326fb8cf080e8fa0b4737c897fc790633a0
CRs-Fixed: 955241
In case channel width is defined to be CH_WIDTH_MAX; channel width
set to CH_WIDTH_80P80MHZ. This can be incorrect if the secondary
frequency segment is not defined. So conditionally set maximum
channel width to CH_WITH_160MHZ.
CRs-Fixed: 1082221
Change-Id: Iff28c56de56e5481814b4710eb51920a88f0f5f7
In function __lim_process_sme_register_mgmt_frame_req, check for
return of qdf_list_remove_node before freeing node.
Change-Id: Ie52f298427e5b006b95f5248ce588d97e2c6aa72
CRs-Fixed: 1081795
qcacld-2.0 to qcacld-3.0 propagation
When restarting SAP due to unsafe channel list, make sure to set
the acs_channel and sapConfig.channel to 0. Otherwise these
parameters overides the ACS logic.
Change-Id: I52d8575960e4d5bac5aa509df41c20fb846a96e6
CRs-Fixed: 1031468
Currently channel zero is configured by sigma dut when reassoc
to same AP is issued. This results in failure as this is invalid
channel. Fix this by passing channel of connected AP.
Change-Id: I1fbdc10256b59d7ca49256461244566e04a52df5
CRs-Fixed: 1081234
In function csr_roam_offload_scan do not populate ASSOC IE(which are only
required in connected_state) in a non-connected state. Otherwise it will
access connected BSS descriptor which is not avaiable in non-connected state.
Change-Id: I9cb0b6f6a49b25c2bd74c5e2140e8fe8919f3f44
CRs-Fixed: 1081198
Host driver reports TX ACK status as success when FW sends
failure status. Due to this supplicant is not retrying the
P2P confirmation frame resulting in Go Negotiation failure.
P2P negotiation state machine can be messed up for other
negotiation action frames as well.
Change-Id: I9a22bd542aea32c7cbac11107fe8b6c9785a2ac1
CRs-Fixed: 1079970
The CLD driver does not compile when FEATURE_WLAN_CH_AVOID is not
defined. Fix related issues.
Change-Id: I3c3f14c16bd6a004670b6105231e591a13039fdc
CRs-Fixed: 1078863
The minimum bandwidth supported is 5 MHZ. Kernel API
wiphy_apply_custom_regulatory can enable channels 12/13
with BW 5/10 even for reg rule 2402-2472. Circumvent the issue
by doing a check in the driver.
Change-Id: I9ad600eda2e507312a3016aa6d1fe6fdc41724f2
CRs-Fixed: 1079851
During driver un-initialization, cds scheduler is closed after
un-initializing lower layer modules. This may lead to crash as
there is possibility of MC thread to process commands after
lower layer objects are uninitialized/freed.
Un-initialize lower layer modules after closing cds schedulers.
Change-Id: Ia43ca4f95c5b40aeb14976b523008e650ba26e10
CRs-Fixed: 1079196
Propagation from qcacld-2.0 to qcacld-3.0.
Error level logs should be used only for error conditions.
Add changes to move unwanted logs to info level.
Change-Id: Ib5b3e1235ad36cf0594291f33e84758261e4d422
CRs-Fixed: 1049765
