While sending message from one module to another module,
bss descriptors' memory get assigned but never get released which
creates memory leaks.
Release bss descriptors' memory up on its usage.
CRs-Fixed: 2040435
Change-Id: I7d9ef4e9b65f4b63251490f4ef3671a350ebf81f
qcacld-2.0 to qcacld-3.0 propagation
MAC layer counters such as per channel signal quality,
per peer TX/RX statistics, are monitored by FW.
FW reports these counters periodically as host setting.
This change:
- Add one parameter to enable/disable mac counter
- Convert FW indication to NL80211 attributes and send the
same to user layer
- Convert user layer's NL80211 attributes to parameters for
link layer monitor and send the same to WMA
Change-Id: I17a81fcec96076e14ff9f33d0aeb0983a25de912
CRs-fixed: 1071059
Remove flooding log from hdd_ipa_nbuf_cb.
Also fix INVALID REASON log from hdd_ipa_uc_op_cb even when
hdd_ipa_uc_op_metering() is succeeded.
Change-Id: Ided529cca3d84cbc3dd6b33dd31fa9086489a176
CRs-Fixed: 1116111
vdev and pool could be NULL during processing the forwarding packets
processed during the driver deinit.
Add a code to return false if pool is NULL in ol_txrx_fwd_desc_thresh_
check(), then the caller will discard the packet without any further
processing.
Also return false when vdev is NULL.
Change-Id: I45afcbe0e8b953bd1be7b3f1f5315f35879edec5
CRs-Fixed: 1112619
Currently, Host configures ITO/TX_Wake_Threshold on each
suspend and resume along LI/DTIM setting. But in a case
where LI/DTIM is configured by user then host skip to
change LI/DTIM values. Hence host skip ITO/TX_Wake_Threshold
configuration too.
As a part of the fix, Decouple ITO/TX_Wake_Threshold from LI/DTIM
configuration.
Change-Id: Ie1c8b7821dcba89d888e18dd7726958a9381e038
CRs-Fixed: 2038986
Present wlansap_close API walks out without releasing the sapctx when
hal context is null which creates the memory leak.
Release sapctx in all cases when caller requests to close the
sap session.
CRs-Fixed: 2040045
Change-Id: I3c8f0a33c11de9d88d6b29f726f36a838f2428d2
Current debug code incorrectly releases parent skb multiple times
while traversing the skb_list. Fix the bug by releasing individual
skbs in a list.
Change-Id: I7047dfc07407275aa7f06cb22840023331ec186f
CRs-Fixed: 2040538
Add TSO segment debug code, in a featurized way, so that
when disabled it will tolerate redundant returns to the internal
pool and when enabled will check sanity on free, and record a
history of last 16 actions on the segment in the object.
Goes with the corresponding cmn component counterpart.
Change-Id: Ifab52fc2032da4d53b708b3c6716d5270c0690c1
CRs-Fixed: 2031485
Limit the detection of non posted rx buffers from FW only to
64 bit DMA address system. For systems, where IPA has 32 bit
DMA address limitation, this debug feature should be disabled.
CRs-Fixed: 2010583
Change-Id: I9a26d0a423acedb068d99f39929029182f7c6fa1
P2P-GO whenever goes offchannel, issues NOA. With this behavior, we
have issue whenever legacy STA connects to P2P-GO as legacy STA
does not understand NOA. To handle this case, changes are done in HDD
and SAP component and the revised behavior will be:
1. By default no change in NOA.
2. Whenever first legacy STA connects to GO, SAP informs HDD with
new parameter station type. HDD will communicate the same to
p2p protocol component. Once the connected station is authorized
p2p protocol component will disable NOA (i.e. P2P-GO will start
issuing Self-CTS whenever it goes off-channel).
3. Whenever last legacy STA disconnects from GO, p2p protocol
component enables NOA (i.e. P2P-GO will start issuing NOA whenever
it goes off-channel).
Change-Id: Iadab47c9a2aeb434371d4c262623d7196f3b1ab4
CRs-Fixed: 2035609
Fix memory leaks of TSO num segments by freeing remaining
TSO num segments in ol_tx_ll_fast and ol_tx_ll if somehow
allocated tx desc is NULL.
Change-Id: I577a95b784c776633cf685cd16b101755a48c521
CRs-Fixed: 2014587
TX BUF POOL vaddr storage alloc is not freed in
htt_tx_ipa_uc_attach when paddr storage allocation fails.
Fix is to free memory in failure case.
CRs-Fixed: 2034943
Change-Id: Ifb26dfdcff19b3ab66f11a89b9c185777eeec535
In csr_scan_copy_request_valid_channels_only(), the DFS channels
are ignored if ini parameter gSkipDfsChannelInP2pSearch is enabled.
If the supplicant issues a single channel scan for a DFS channel,
driver will do a full scan. As its a single channel scan which is a
DFS channel would be ignored and the num of channels to scan would
be zero.
And if the number of channels to scan are zero, driver
does a full scan which would impact the overall connection
time.
To address this, enable DFS channel for a single
channel scan.
Change-Id: I166b9674a6cb6bb9c180c1c8d68480440ea867be
CRs-Fixed: 2038974
In a case when a STA interface is existing and AP/GO comes up as the second
interface, it might happen that the 'scan list' of the existing STA
interface has not been refreshed yet.
It might be displaying a third-party-AP which is on a different
channel than our AP/GO-interface.
If the STA tries to connect to the third-party-AP, then the connection
is rejected if
1) Do_Not_Switch_Channel is set for the AP/GO vdev
AND
2) The third-party-AP channel is on the same band but is different from the
AP/GO-interface channel.
If the third-party-AP and our AP/GO-interface channels are same OR in
different bands, then the connection is allowed to go through.
Change-Id: I940665ac38864cc8a16912c714412dd4c8d819d6
CRs-Fixed: 2036903
It might happen that the STA-interface is in the process of
associating and before association is complete,
"Do_Not_Switch_Channel" is enabled on the AP-interface.
Reject STA association if "Do_Not_Switch_Channel" is enabled.
A check is performed in hdd_association_completion_handler() for
"Do_Not_Switch_Channel" in AP/GO vdev and STA association is
rejected accordingly.
Change-Id: I3f319a9e14c28add68f9809eeb86e782e58e72de
CRs-Fixed: 2036942
center frequency of 40/80/160 are not valid frequency
for regulatory component, so regulatory api's may not
covert freq to channel or chan to freq. use dfs api’s
to covert the same.
Change-Id: I3bb7d4997d0dbcbd757537fe3fee9ad5f7f97904
CRs-Fixed: 2017481
wma_wow_wakeup_host_event is a large monolithic function with many
responsibilities. Break this function up into smaller pieces for each
of those responsibilities to make moving this logic to the component
model easier.
Change-Id: I5583aad21280a6fbf97c7634c9c9763be61fedc3
CRs-Fixed: 2038488
