Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit ee91d185 authored by Eyal Shapira's avatar Eyal Shapira Committed by Luciano Coelho
Browse files

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: default avatarEyal Shapira <eyal@wizery.com>
Signed-off-by: default avatarLuciano Coelho <coelho@ti.com>
parent fea2a613

drivers/net/wireless/wl12xx/event.c

+1 −1
Original line number Diff line number Diff line
@@ -267,8 +267,8 @@ static int wl1271_event_process(struct wl1271 *wl, struct event_mailbox *mbox) 
		wl1271_debug(DEBUG_EVENT, "PERIODIC_SCAN_COMPLETE_EVENT "

			     "(status 0x%0x)", mbox->scheduled_scan_status);

		if (wl->sched_scanning) {

			wl1271_scan_sched_scan_stop(wl);

			ieee80211_sched_scan_stopped(wl->hw);

			wl->sched_scanning = false;

		}

	}

drivers/net/wireless/wl12xx/scan.c

+0 −1
Original line number Diff line number Diff line
@@ -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);