ath10k: don't forget to replenish after fragmented Rx
authorMichal Kazior <michal.kazior@tieto.com>
Thu, 23 Oct 2014 14:04:24 +0000 (17:04 +0300)
committerKalle Valo <kvalo@qca.qualcomm.com>
Fri, 24 Oct 2014 13:30:00 +0000 (16:30 +0300)
commit686687c9afb43d396b32689f4dd29d1e87cebdf8
treef3b60409f2c2264b99dfbd04ef25ce38b7244912
parentb30595aea39d6946c1d17c3f278fb8d2fbe2a4cf
ath10k: don't forget to replenish after fragmented Rx

In theory it was possible to drain entire HTT Rx
ring via fragmented Rx leading to Rx lockup.

In practice non-data traffic would always trigger
replenishment via the regular Rx handler.

For correctness sake make sure to replenish the
ring on fragmented Rx.

Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
drivers/net/wireless/ath/ath10k/htt_rx.c