forked from Minki/linux
c743627388
When the driver receives "connection terminated" event from device, it could be caused by 2 reasons: the firmware is roaming or the connection is lost (AP disappears). For the former, an association complete event is supposed to come within 3 seconds. For the latter, the driver won't receive any event except the connection terminated. So we kick a delayed work (5*HZ) when we receive the connection terminated event. It will be canceled if it turns out to be a roaming event later. Otherwise we notify SME and userspace the disconnection. Signed-off-by: Zhu Yi <yi.zhu@intel.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> |
||
|---|---|---|
| .. | ||
| bus.h | ||
| cfg80211.c | ||
| cfg80211.h | ||
| commands.c | ||
| commands.h | ||
| debug.h | ||
| debugfs.c | ||
| eeprom.c | ||
| eeprom.h | ||
| fw.c | ||
| fw.h | ||
| hal.c | ||
| hal.h | ||
| iwm.h | ||
| Kconfig | ||
| lmac.h | ||
| main.c | ||
| Makefile | ||
| netdev.c | ||
| rx.c | ||
| rx.h | ||
| sdio.c | ||
| sdio.h | ||
| tx.c | ||
| umac.h | ||