Update correct check while unpacking PPE threshold. Incorrect
placement of parentheses may lead to unexpected behavor.
Change-Id: If1af2ab7a0601e4a25183cb8fbaf0dfd99e9bf58
CRs-Fixed: 1073481
Update HE ops correctly in vdev start request. Currently the update
is done in a local copy and is not updating the vdev start request.
Fix is to copy the local he ops value into vdev start request.
Change-Id: Ife5b40a8df3d6a47c2f170efdb7aae009bb8be95
CRs-Fixed: 1073481
Decrement the peer ref cnt incremented while getting peer through
wlan_objmgr_get_peer() to pass it to wlan_mgmt_txrx_mgmt_frame_tx().
Change-Id: I2791075d63610d76fa1c70d3efe76df2b2618b01
CRs-Fixed: 2025052
TDLS mutex is not unlocked properly in few error instances.
Thus, the thread gets stuck.
The fix is to unlock mutex properly before returning.
Change-Id: Ic16015e568dd91af17b3bb1ba9b19722cb0f82d9
CRs-Fixed: 2026737
Add a HDD callback to get the type of a non connected vdev
needed by policy manager.
Change-Id: I9e0666217f7f4fef3d754534a83295f5e47b0ab9
CRs-Fixed: 2009818
Functionality to send the P2P QUOTA and MCC LATENCY values to FW
is moved back to HDD since the policy manager is not using them.
Change-Id: Ia084035a27056dab6ed8d66cab2687c2f697fb4c
CRs-Fixed: 2019994
After removing legacy policy manager header file had to add
correct header files from host common to allow the compilation
to happen successfully.
Change-Id: I566b8f09776520e8a43eb48cc944ce627dc0c5cf
CRs-Fixed: 2009818
Remove reference to legacy policy manager API to cope with
the policy manager moving to host common.
Change-Id: I5d2d4f497b02a4c701cd83e319d533c328be48cd
CRs-Fixed: 2009818
Replace policy manager header file include as part of policy manager
moving to host common.
Change-Id: Ie1f9d6675cc373c3325c9e76514f48299932cdda
CRs-Fixed: 2009818
Remove legacy policy manager code as part of policy manager moving to host
common.
Change-Id: I6cb9fe12bee3702556c9b52e7ccb7c69c762d8de
CRs-Fixed: 2009818
Currently hdd_release_and_destroy_pdev() retrieves and resets the
pdev's ospriv data pointer by directly dereferencing the pdev
object. This is not the correct object-oriented approach. Instead of
dereferencing the object, invoke the wlan_pdev_get_ospriv() and
wlan_pdev_reset_ospriv() methods that exists for this purpose.
Change-Id: I71a5d090648b76261d863a0b0168a83cdf9911b3
CRs-Fixed: 2024022
Currently hdd_release_and_destroy_vdev() resets the vdev's ospriv data
pointer by directly dereferencing the vdev object. This is not the
correct object-oriented approach. Instead of dereferencing the object,
invoke the wlan_vdev_reset_ospriv() method that exists for this
purpose.
Change-Id: I68a504b022933a47276d5c76c079472e8d3a6402
CRs-Fixed: 2024020
Interface change timer is wrongly multiplied by 50000 leading
to very large timeout value and FW getting stuck in ON state
even if there is no active interface and leading to battery drain.
Fix the battery drain issue by removing the wrong multiplication.
Change-Id: Icc23bc6c666c2e474c17c9a5175ca54721861e0d
CRs-Fixed: 2017489
This change includes to drop RX mgmt packets before sending to MC thread
context based on below conditions
1) Print an warn message when no.of pending RX packets reaches to
1/4th of threshold
2) Drop probe req, probe resp and beacon frames when
no.of pending RX packets reaches to 1/2 of threshold
3) Drop all the RX management packets when no.of pending RX packets
equals to threshold
Add a counter to maintain no.of pending management packets in queue
and MGMT_RX_PACKETS_THRESHOLD for threshold value
Change-Id: I9428a1a054f717a285378dbe95592ba0c5c569e6
CRs-Fixed: 2011645
qcacld-2.0 to qcacld-3.0 propagation
AP1 starts on 2.4g, AP2 starts on 5g ht40.
The AP2 is always failed to find the interference
AP during OBSS scan. It is because the cld driver
uses passive scan but the dwell time is set to
active scan's default dwell time 80ms. That is too
short for passive scan.
The fix is to set the dwell time based on scan type.
Change-Id: I687217f7d15f963f0043dab661ae29bb026ba7b5
CRs-Fixed: 1093940
Memory is not freed in csr_process_set_hw_mode in the
failure case when connection or bt coex is in progress.
Fix is to free memory in failure case.
Change-Id: I6be164c516ce30d5def7b0088c8b62d6409acf6a
CRs-Fixed: 2024748
FTM mode is purely a testing mode. As such, crashes in firmware should
not be gracefully handled. Instead, crash the system to produce a crash
dump to aid in the debugging process.
Change-Id: Ie4098b02be39a25c00f839566d35456bad5834d6
CRs-Fixed: 2025877
