> What I changed is triggerring the scan work whenever the last > one is done, i.e. triggering it from lbs_ret_scan(). Ah, that makes sense. > My initial thought was that you could have 2 lbs_cfg_scan() > running at the same time since you could potentially have a 2nd > lbs_cfg_scan() call before scan_request is actually set. Hmm, even when cfg80211 would allow this, I wouldn't allow this in the driver. All the hoops with the delayed-scan-work is because the firmware can't send a I'm-on-powersafe-notification to the current AP while being on other channels. So I have to make sure to return from time to time to my AP, so that I won't loose packets for me and won't be disconnected. If now two scan_req and therefore two scan workers run, the time we're away from our "home channel" increases, which also increase the deauthentication problem. Oh, and btw: we can later add an optimization that if we aren't connected at all, we do all scans in one-go, without delays. We still need to send several scan-commands to the firmware, to reduce the possible that a huuuuuge scan response overflows some firmware buffer limit. Thanks for your answers. Best regards, Holger -- http://www.holgerschurig.de -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
