1 From: Felix Fietkau <nbd@openwrt.org>
2 Date: Sat, 18 Oct 2014 13:31:52 +0200
3 Subject: [PATCH] ath9k: fix processing RXORN interrupts
5 The "goto chip_reset" is a bit misleading, because it does not actually
6 issue a chip reset. Instead it is bypassing processing of other
7 interrupts and assumes that the tasklet will issue a chip reset.
9 In the case of RXORN this does not happen, so bypassing processing of
10 other interrupts will simply allow them to fire again. Even if RXORN
11 was triggering a reset, it is not critical enough to need the bypass
14 Signed-off-by: Felix Fietkau <nbd@openwrt.org>
17 --- a/drivers/net/wireless/ath/ath9k/main.c
18 +++ b/drivers/net/wireless/ath/ath9k/main.c
19 @@ -545,11 +545,10 @@ irqreturn_t ath_isr(int irq, void *dev)
23 - * If a FATAL or RXORN interrupt is received, we have to reset the
25 + * If a FATAL interrupt is received, we have to reset the chip
28 - if ((status & ATH9K_INT_FATAL) || ((status & ATH9K_INT_RXORN) &&
29 - !(ah->caps.hw_caps & ATH9K_HW_CAP_EDMA)))
30 + if (status & ATH9K_INT_FATAL)
33 if ((ah->config.hw_hang_checks & HW_BB_WATCHDOG) &&