ath9k: Fix queue handling for channel contexts
When a full chip reset is done, all the queues across all VIFs are stopped, but if MCC is enabled, only the queues of the current context is awakened, when we complete the reset. This results in unfairness for the inactive context. Since frames are queued internally in the driver if there is a context mismatch, we can awaken all the queues when coming out of a reset. The VIF-specific queues are still used in flow control, to ensure fairness when traffic is high. Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
This commit is contained in:
parent
a064eaa10c
commit
5ba8d9d2f0
|
@ -264,12 +264,7 @@ static bool ath_complete_reset(struct ath_softc *sc, bool start)
|
|||
|
||||
ath9k_hw_set_interrupts(ah);
|
||||
ath9k_hw_enable_interrupts(ah);
|
||||
|
||||
if (!ath9k_is_chanctx_enabled())
|
||||
ieee80211_wake_queues(sc->hw);
|
||||
else
|
||||
ath9k_chanctx_wake_queues(sc, sc->cur_chan);
|
||||
|
||||
ath9k_p2p_ps_timer(sc);
|
||||
|
||||
return true;
|
||||
|
|
Loading…
Reference in New Issue