| commit | 92ef8960aee2f840c6a54c968d40199843f015c0 | |
| author | Eliad Peller <eliad@wizery.com> | |
| Tue, 7 Jun 2011 09:50:46 +0000 (7 12:50 +0300) | ||
| committer | Luciano Coelho <coelho@ti.com> | |
| Mon, 27 Jun 2011 10:56:14 +0000 (27 13:56 +0300) | ||
| tree | 3554b6b9684c7fe5cfabdb9ea15a9dd2d3640f50 | treesnapshot (tar.gz zip) |
| parent | c27d3accb6f06b0afedfe472dfe0c8e7d87ff0a6 | commitdiff |
wl12xx: use freezable workqueue for netstack_work
When resuming (after wowlan), we want the rx packets (which is
usually the wake-up packet itself) to be passed to mac80211 only
after the resume notifier was completed, and mac80211 is up and
running (otherwise, the packets will be dropped).
By enqueueing the netstack_work to a freezable workqueue, we can
guarantee the rx processing to occur only after mac80211 was resumed.
Signed-off-by: Eliad Peller <eliad@wizery.com>
Signed-off-by: Ido Yariv <ido@wizery.com>
Signed-off-by: Luciano Coelho <coelho@ti.com>
When resuming (after wowlan), we want the rx packets (which is
usually the wake-up packet itself) to be passed to mac80211 only
after the resume notifier was completed, and mac80211 is up and
running (otherwise, the packets will be dropped).
By enqueueing the netstack_work to a freezable workqueue, we can
guarantee the rx processing to occur only after mac80211 was resumed.
Signed-off-by: Eliad Peller <eliad@wizery.com>
Signed-off-by: Ido Yariv <ido@wizery.com>
Signed-off-by: Luciano Coelho <coelho@ti.com>