forked from Minki/linux
18b559d5db
When TX aggregation is stopped, there are a few different cases: - connection with the peer was dropped - session stop was requested locally - session stop was requested by the peer - connection was dropped while a session is stopping The behaviour in these cases should be different, if the connection is dropped then the driver should drop all frames, otherwise the frames may continue to be transmitted, aggregated in the case of a locally requested session stop or unaggregated in the case of the peer requesting session stop. Split these different cases so that the driver can act accordingly; however, treat local and remote stop the same way and ask the driver to not send frames as aggregated packets any more. In the case of connection drop, the stop callback the driver is otherwise supposed to call is no longer required. Signed-off-by: Johannes Berg <johannes.berg@intel.com> |
||
|---|---|---|
| .. | ||
| agn.h | ||
| calib.c | ||
| calib.h | ||
| commands.h | ||
| debugfs.c | ||
| dev.h | ||
| devices.c | ||
| led.c | ||
| led.h | ||
| lib.c | ||
| mac80211.c | ||
| main.c | ||
| Makefile | ||
| power.c | ||
| power.h | ||
| rs.c | ||
| rs.h | ||
| rx.c | ||
| rxon.c | ||
| scan.c | ||
| sta.c | ||
| testmode.c | ||
| tt.c | ||
| tt.h | ||
| tx.c | ||
| ucode.c | ||