android_kernel_xiaomi_sm8350/core
yeshwanth sriram guntuka 7f4cb34431 qcacld-3.0: Fix connect failure due to scan stuck
Peer sta kickout ind was received from fw nine times
which resulted in queuing nine scan commands as part
of csr_scan_request_lost_link1 without checking for
max allowed scans. The ninth scan cmd is not released
as fw did not send completion event resulting in
subsequent connect to fail.

Fix is to
1) check for max allowed scans before
queuing scan command.
2) check for lim sme state to avoid invoking tear
down link with ap multiple times on receiving
multiple peer sta kickout ind from fw.
3) don't invoke csr_scan_request_lost_link1 as part
of csr_roam_lost_link as supplicant will issue scan
after successful disconnection.

Change-Id: I850fd336fc73e4b2c2362dfd11db433b68ccd1fb
CRs-Fixed: 2031342
2017-05-21 23:55:48 -07:00
..
bmi qcacld-3.0: Update for check patch refactoring 2017-05-02 13:29:40 -07:00
cds qcacld-3.0: Add support for regulatory component ucfg apis 2017-05-18 13:42:29 -07:00
dp qcacld-3.0: Reduce failure log level of OL_TX_SEND 2017-05-19 14:50:38 -07:00
hdd qcacld-3.0: Handle bss color change IE coming from AP 2017-05-19 15:57:47 -07:00
mac qcacld-3.0: Fix connect failure due to scan stuck 2017-05-21 23:55:48 -07:00
pld qcacld-3.0: Add PLD APIs to support athdiag read/write 2017-05-18 13:42:32 -07:00
sap qcacld-3.0: Fix memory leak in restart bss path 2017-05-19 11:06:34 -07:00
sme qcacld-3.0: Fix connect failure due to scan stuck 2017-05-21 23:55:48 -07:00
wma qcacld-3.0: Handle bss color change IE coming from AP 2017-05-19 15:57:47 -07:00