From: greearb@candelatech.com
To: linux-wireless@vger.kernel.org
Cc: ath10k@lists.infradead.org, Ben Greear <greearb@candelatech.com>
Subject: [PATCH v3 2/5] ath10k: save firmware debug log messages.
Date: Tue, 22 Jul 2014 16:02:31 -0700 [thread overview]
Message-ID: <1406070154-6614-2-git-send-email-greearb@candelatech.com> (raw)
In-Reply-To: <1406070154-6614-1-git-send-email-greearb@candelatech.com>
From: Ben Greear <greearb@candelatech.com>
They may be dumped through the firmware dump debugfs
file.
Signed-off-by: Ben Greear <greearb@candelatech.com>
---
drivers/net/wireless/ath/ath10k/wmi.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/net/wireless/ath/ath10k/wmi.c b/drivers/net/wireless/ath/ath10k/wmi.c
index 6f83cae..df62115 100644
--- a/drivers/net/wireless/ath/ath10k/wmi.c
+++ b/drivers/net/wireless/ath/ath10k/wmi.c
@@ -1089,6 +1089,12 @@ static int ath10k_wmi_event_debug_mesg(struct ath10k *ar, struct sk_buff *skb)
trace_ath10k_wmi_dbglog(skb->data, skb->len);
+ /* First 4 bytes are a messages-dropped-due-to-overflow counter,
+ * and should not be recorded in the dbglog buffer, so we skip
+ * them.
+ */
+ ath10k_dbg_save_fw_dbg_buffer(ar, skb->data + 4, skb->len - 4);
+
return 0;
}
--
1.7.11.7
next prev parent reply other threads:[~2014-07-22 23:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 23:02 [PATCH v3 1/5] ath10k: provide firmware crash info via debugfs greearb
2014-07-22 23:02 ` greearb [this message]
2014-07-22 23:02 ` [PATCH v3 3/5] ath10k: save firmware stack upon firmware crash greearb
2014-07-22 23:02 ` [PATCH v3 4/5] ath10k: Dump exception stack contents on " greearb
2014-07-22 23:02 ` [PATCH v3 5/5] ath10k: save firmware RAM and ROM BSS sections on crash greearb
2014-07-23 8:25 ` [PATCH v3 1/5] ath10k: provide firmware crash info via debugfs Michal Kazior
2014-07-23 8:34 ` Emmanuel Grumbach
2014-07-23 12:45 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1406070154-6614-2-git-send-email-greearb@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).