From: Ben Greear <greearb@candelatech.com>
To: Rakesh Pillai <pillair@codeaurora.org>, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath10k: Add history for tracking certain events
Date: Sat, 27 Jun 2020 08:28:11 -0700 [thread overview]
Message-ID: <926301ed-e27f-0d8f-0177-6484bfffa40c@candelatech.com> (raw)
In-Reply-To: <1593238973-23237-1-git-send-email-pillair@codeaurora.org>
On 06/26/2020 11:22 PM, Rakesh Pillai wrote:
> For debugging many issues, a history of the
> below mentioned events can help get an idea
> of what exactly was going on just before any
> issue occurred in the system. These event
> history will be collected only when the host
> driver is run in debug mode (i.e. with the
> config ATH10K_DEBUG enabled).
This should be disabled by default unless user specifically pokes some debugfs
value to turn it on so that it does not impact performance.
Thanks,
Ben
>
> Add history for tracking the below events
> - register read
> - register write
> - IRQ trigger
> - IRQ Enable
> - IRQ Disable
> - NAPI poll
> - CE service
> - WMI cmd
> - WMI event
> - WMI tx completion
>
> This will help in debugging any crash or any
> improper behaviour.
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2020-06-27 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 6:22 [PATCH] ath10k: Add history for tracking certain events Rakesh Pillai
2020-06-27 15:28 ` Ben Greear [this message]
2020-06-28 5:12 ` Rakesh Pillai
2020-06-28 17:25 ` Ben Greear
2020-07-16 11:48 ` Rakesh Pillai
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=926301ed-e27f-0d8f-0177-6484bfffa40c@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pillair@codeaurora.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).