Print firmware and ucode assert codes when firmware crashed.

Signed-off-by: Lior David <li...@qti.qualcomm.com>
Signed-off-by: Vladimir Kondratiev <qca_vkond...@qca.qualcomm.com>
---
 drivers/net/wireless/ath/wil6210/interrupt.c | 7 ++++++-
 drivers/net/wireless/ath/wil6210/wil6210.h   | 4 ++++
 2 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/drivers/net/wireless/ath/wil6210/interrupt.c 
b/drivers/net/wireless/ath/wil6210/interrupt.c
index a371f036..f651994 100644
--- a/drivers/net/wireless/ath/wil6210/interrupt.c
+++ b/drivers/net/wireless/ath/wil6210/interrupt.c
@@ -347,7 +347,12 @@ static irqreturn_t wil6210_irq_misc(int irq, void *cookie)
        wil6210_mask_irq_misc(wil);
 
        if (isr & ISR_MISC_FW_ERROR) {
-               wil_err(wil, "Firmware error detected\n");
+               u32 fw_assert_code = wil_r(wil, RGF_FW_ASSERT_CODE);
+               u32 ucode_assert_code = wil_r(wil, RGF_UCODE_ASSERT_CODE);
+
+               wil_err(wil,
+                       "Firmware error detected, assert codes FW 0x%08x, UCODE 
0x%08x\n",
+                       fw_assert_code, ucode_assert_code);
                clear_bit(wil_status_fwready, wil->status);
                /*
                 * do not clear @isr here - we do 2-nd part in thread
diff --git a/drivers/net/wireless/ath/wil6210/wil6210.h 
b/drivers/net/wireless/ath/wil6210/wil6210.h
index e405bef..525ce2c 100644
--- a/drivers/net/wireless/ath/wil6210/wil6210.h
+++ b/drivers/net/wireless/ath/wil6210/wil6210.h
@@ -246,6 +246,10 @@ struct RGF_ICR {
 #define RGF_USER_JTAG_DEV_ID   (0x880b34) /* device ID */
        #define JTAG_DEV_ID_SPARROW_B0  (0x2632072f)
 
+/* crash codes for FW/Ucode stored here */
+#define RGF_FW_ASSERT_CODE             (0x91f020)
+#define RGF_UCODE_ASSERT_CODE          (0x91f028)
+
 enum {
        HW_VER_UNKNOWN,
        HW_VER_SPARROW_B0, /* JTAG_DEV_ID_SPARROW_B0 */
-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to