path: root/wpa_supplicant/scan.h
diff options
authorJithu Jance <jithu@broadcom.com>2013-10-17 06:26:02 (GMT)
committerJouni Malinen <j@w1.fi>2013-11-18 12:35:48 (GMT)
commitf86d282f4326fac4a945094bd8f06c9ee1f3087e (patch)
treeb7def5a58c2ab4149efe055f404fd454bf8fd3ba /wpa_supplicant/scan.h
parentc41e1d7cace6c84c767c4540eb807dea7f6da9ad (diff)
Handle legacy scan interruption of sched_scan/PNO
While starting from PNO start context, the scheduled scan was not setting the flag wpa_s->scanning. This was resulting in the subsequent SCAN command to proceed further and send command to nl80211/cfg80211. The expected behavior of cancelling sched_scan was not happening here. While sched_scan is in progress and a legacy scan comes on the cli/socket, the sched_scan is cancelled and normal scan is allowed to continue. However, sometimes sched_scan cancelled event comes a bit delayed and we will send out the scan command before the wpa_s->scanning is cleared. Instead, reschedule the incoming scan req if the wpa_s->scanning shows that it is still in progress. Signed-hostap: Jithu Jance <jithu@broadcom.com>
Diffstat (limited to 'wpa_supplicant/scan.h')
1 files changed, 4 insertions, 0 deletions
diff --git a/wpa_supplicant/scan.h b/wpa_supplicant/scan.h
index 66581a9..b6fe070 100644
--- a/wpa_supplicant/scan.h
+++ b/wpa_supplicant/scan.h
@@ -39,5 +39,9 @@ void wpa_supplicant_update_scan_int(struct wpa_supplicant *wpa_s, int sec);
void scan_only_handler(struct wpa_supplicant *wpa_s,
struct wpa_scan_results *scan_res);
int wpas_scan_scheduled(struct wpa_supplicant *wpa_s);
+int wpa_supplicant_start_sched_scan(struct wpa_supplicant *wpa_s,
+ struct wpa_driver_scan_params *params,
+ int interval);
+int wpa_supplicant_stop_sched_scan(struct wpa_supplicant *wpa_s);
#endif /* SCAN_H */