As soon as debugging is turned on, the logs are filled with messages
reporting the interrupt status. As this quantity is usually zero, this
output is not needed. In fact, there will be a report if the status is
not zero, thus the debug line in question could probably be deleted.
Rather than taking that action, I have changed it to only be printed
when the newly added RTL8XXXU_DEBUG_INTERRUPT bit is set in the debug

Signed-off-by: Larry Finger <>
V2 - Added new debugging flag as requested by Jes.
 drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h      | 1 +
 drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c | 3 ++-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h 
index 870c9cd..4508b6d 100644
--- a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h
+++ b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h
@@ -29,6 +29,7 @@
 #define RTL8XXXU_DEBUG_H2C             0x800
 #define RTL8XXXU_DEBUG_ACTION          0x1000
 #define RTL8XXXU_DEBUG_EFUSE           0x2000
+#define RTL8XXXU_DEBUG_INTERRUPT       0x4000
 #define RTL8XXXU_MAX_REG_POLL          500
diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c 
index 9f6dbb4..efba8f1 100644
--- a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
+++ b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
@@ -5260,7 +5260,8 @@ static void rtl8xxxu_int_complete(struct urb *urb)
        struct device *dev = &priv->udev->dev;
        int ret;
-       dev_dbg(dev, "%s: status %i\n", __func__, urb->status);
+       if (rtl8xxxu_debug & RTL8XXXU_DEBUG_INTERRUPT)
+               dev_dbg(dev, "%s: status %i\n", __func__, urb->status);
        if (urb->status == 0) {
                usb_anchor_urb(urb, &priv->int_anchor);
                ret = usb_submit_urb(urb, GFP_ATOMIC);

Reply via email to