ath9k: make some hardware reset log messages debug-only

On some chips, baseband watchdog hangs are more common than others, and
the driver has support for handling them.
Interrupts even after a watchdog hang are also quite common, so there's
not much point in spamming the user's logfiles.

Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>

diff --git a/drivers/net/wireless/ath/ath9k/main.c b/drivers/net/wireless/ath/ath9k/main.c
index afce549..14a7524 100644 (file)
--- a/drivers/net/wireless/ath/ath9k/main.c
+++ b/drivers/net/wireless/ath/ath9k/main.c
@@ -451,7 +451,7 @@ void ath9k_tasklet(unsigned long data)
                 * interrupts are enabled in the reset routine.
                 */
                atomic_inc(&ah->intr_ref_cnt);
-               ath_dbg(common, ANY, "FATAL: Skipping interrupts\n");
+               ath_dbg(common, RESET, "FATAL: Skipping interrupts\n");
                goto out;
        }
 
@@ -471,7 +471,7 @@ void ath9k_tasklet(unsigned long data)
                         * interrupts are enabled in the reset routine.
                         */
                        atomic_inc(&ah->intr_ref_cnt);
-                       ath_dbg(common, ANY,
+                       ath_dbg(common, RESET,
                                "BB_WATCHDOG: Skipping interrupts\n");
                        goto out;
                }
@@ -484,7 +484,7 @@ void ath9k_tasklet(unsigned long data)
                        type = RESET_TYPE_TX_GTT;
                        ath9k_queue_reset(sc, type);
                        atomic_inc(&ah->intr_ref_cnt);
-                       ath_dbg(common, ANY,
+                       ath_dbg(common, RESET,
                                "GTT: Skipping interrupts\n");
                        goto out;
                }