wlcore: print stack trace in every recovery
authorEyal Shapira <eyal@wizery.com>
Tue, 26 Jun 2012 07:41:17 +0000 (10:41 +0300)
committerLuciano Coelho <coelho@ti.com>
Tue, 26 Jun 2012 17:33:42 +0000 (20:33 +0300)
As recovery queuing can now occur from multiple code paths
it's convenient to know what triggered it in all cases
other than an intended recovery which is part of the
switch between single role to multi role.

Signed-off-by: Eyal Shapira <eyal@wizery.com>
Signed-off-by: Luciano Coelho <coelho@ti.com>
drivers/net/wireless/ti/wlcore/cmd.c
drivers/net/wireless/ti/wlcore/main.c

index ef139383ee9357b6f99b47b4e3b42bd5a9bfdd10..56c7a2342fdfc54e7487f262d4237ca93a6e0cbd 100644 (file)
@@ -124,7 +124,6 @@ int wl1271_cmd_send(struct wl1271 *wl, u16 id, void *buf, size_t len,
        return 0;
 
 fail:
-       WARN_ON(1);
        wl12xx_queue_recovery_work(wl);
        return ret;
 }
index c5a9ffe6cc914cac5a5e5fba99846bf14b2ae8a2..2240cca597acf812d87a4291aa855d4e39272f90 100644 (file)
@@ -772,6 +772,8 @@ out:
 
 void wl12xx_queue_recovery_work(struct wl1271 *wl)
 {
+       WARN_ON(!test_bit(WL1271_FLAG_INTENDED_FW_RECOVERY, &wl->flags));
+
        /* Avoid a recursive recovery */
        if (!test_and_set_bit(WL1271_FLAG_RECOVERY_IN_PROGRESS, &wl->flags)) {
                wlcore_disable_interrupts_nosync(wl);