summaryrefslogtreecommitdiff
path: root/drivers/net/wireless/wl12xx/scan.c
diff options
context:
space:
mode:
authorEyal Shapira <eyal@wizery.com>2011-12-20 16:55:38 +0400
committerLuciano Coelho <coelho@ti.com>2011-12-21 00:30:16 +0400
commitee91d1855137ba9c16d1e7815d562056c3f55e7f (patch)
tree17e428e7f057f005484613fa2407a78a4e172968 /drivers/net/wireless/wl12xx/scan.c
parentfea2a613cf33ee0662e413e2f5697bed36d5029e (diff)
downloadlinux-ee91d1855137ba9c16d1e7815d562056c3f55e7f.tar.xz
wl12xx: mark no sched scan only after FW event
stop sched scan isn't an immediate operation and we need to wait for PERIODIC_SCAN_COMPLETE_EVENT_ID after sending a stop before changing internal state and notifying upper layers. Not doing this caused problems when canceling an existing sched scan and immediately requesting to start a new one with a different configuration as the FW was still in the middle of the previous sched scan. Signed-off-by: Eyal Shapira <eyal@wizery.com> Signed-off-by: Luciano Coelho <coelho@ti.com>
Diffstat (limited to 'drivers/net/wireless/wl12xx/scan.c')
-rw-r--r--drivers/net/wireless/wl12xx/scan.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/net/wireless/wl12xx/scan.c b/drivers/net/wireless/wl12xx/scan.c
index 05dca0c1d442..e24111ececc5 100644
--- a/drivers/net/wireless/wl12xx/scan.c
+++ b/drivers/net/wireless/wl12xx/scan.c
@@ -754,7 +754,6 @@ void wl1271_scan_sched_scan_stop(struct wl1271 *wl)
wl1271_error("failed to send sched scan stop command");
goto out_free;
}
- wl->sched_scanning = false;
out_free:
kfree(stop);