From: Jouni Malinen <j@w1.fi>
To: Arend van Spriel <arend@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: wpa_supplicant and driver reload
Date: Tue, 14 Jan 2014 18:30:27 +0200 [thread overview]
Message-ID: <20140114163027.GA23034@w1.fi> (raw)
In-Reply-To: <52D55C5C.8010402@broadcom.com>
On Tue, Jan 14, 2014 at 04:48:44PM +0100, Arend van Spriel wrote:
> On 12/15/2013 10:15 AM, Arend van Spriel wrote:
> Found the problem in the way brcmfmac does cleanup upon unload. With
> that fixed I notice some other behaviour. After 3 driver reloads (within
> 1 minute) wpa_supplicant requests a scheduled scan. I fixed that by
> resetting wpa_s->normal_scans to zero upon entering
> WPA_INTERFACE_DISABLED state.
Patch welcome..
> The only thing left is that after each
> reload the delay before requesting a scan increases with 1 second. This
> is caused by the fact that in wpa_supplicant_driver_init() the delay is
> determined by a static counter that increments upon each call (if there
> are enabled networks). I think this is mainly intended for wpa_s startup
> so scans for each interface are not colliding. Not sure what the best
> way is to solve that.
Finishing this stalled discussion:
http://patchwork.ozlabs.org/patch/245486/
And yes, this was added very much for the case of initial start only, so
doing a clean change to limit it for that case should be fine.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2014-01-14 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 9:02 wpa_supplicant and driver reload Arend van Spriel
2013-12-15 5:46 ` Jouni Malinen
2013-12-15 9:15 ` Arend van Spriel
2014-01-14 15:48 ` Arend van Spriel
2014-01-14 16:30 ` Jouni Malinen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140114163027.GA23034@w1.fi \
--to=j@w1.fi \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).