Wlan: Drop connect after scan for ssid if stop adaptor is issued

During connection if AP is not found in scan list, driver tries
to scan for the ssid (eCsrScanForSsid) and if AP is found,
the connect cmd is queued in sme queue.

During this scan if stop adaptor is called as part of unload,
it will try to issue disconnect, but as there is no ongoing
connect command and sme is not in connected state,
the disconnect command is dropped in sme.

In this case driver tries to abort the scan for ssid to stop
the connect command. But a condition arise when scan for ssid
is already completed before abort was issued and thus connect
command is issued.

If this connect command is successful, it will send ADD BSS to
firmware.

Now as stop adapter failed to send disconnect, stop request
will be sent to firmware without DEL BSS. This leads to crash.

To avoid this don't issue connect after scan for ssid, if stop
adapter has called disconnect.

Change-Id: I5d61bf3d6831674e3241b10bded04fc025fd2181
CRs-Fixed: 975008
4 files changed
tree: 2bc70a77e5b1e6cdc172c81d7cd960393ff7fbaa
  1. CORE/
  2. firmware_bin/
  3. riva/
  4. Android.mk
  5. Kbuild
  6. Kconfig
  7. Makefile