summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/tasks.py
diff options
context:
space:
mode:
authorVignesh Viswanathan <viswanat@codeaurora.org>2018-09-24 15:52:47 +0530
committernshrivas <nshrivas@codeaurora.org>2018-09-26 02:09:26 -0700
commit76f3fa19095f7812f048734d77ae6c0d00f6970b (patch)
treec6dfab470e8e0b1e784e4d1e7e5f506e4198ef94 /scripts/gdb/linux/tasks.py
parent43a8225d67c52e6ef577ea4c3900772b7d5974b8 (diff)
qcacld-3.0: Check SME connection status before issuing reassoc
Currently when the supplicant sends a connect with bssid_hint and prev_bssid, driver issues a roam_invoke (fast reassoc) command to the FW. However, when this connect is received in the supplicant context and if the driver is currently processing a disassoc/deauth from the AP in the mc thread, then the CSR roam connection state would not be associated but the HDD STA context connection state would still be associated. In this scenario, since the disconnection is in progress and VDEV Down might already be sent to the FW, the roam_invoke command is ignored and FW does not send any response. However the driver assumes that roaming is in progress and blocks all incoming scan/ connect requests from supplicant leading to a state where no further connections can go through. In hdd_reassoc, check the CSR Connection state also to check if the current state is associated and then issue roam_invoke to FW. Change-Id: I321e99b060d6ce22517a3dd604b0f4d08dd5918d CRs-Fixed: 2319641
Diffstat (limited to 'scripts/gdb/linux/tasks.py')
0 files changed, 0 insertions, 0 deletions