From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v8 2/4] ath10k: provide firmware crash info via debugfs
Date: Thu, 21 Aug 2014 15:10:16 +0200 [thread overview]
Message-ID: <1408626616.4388.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20140821124907.27159.64620.stgit@potku.adurom.net> (sfid-20140821_144916_865910_8B25D7B4)
On Thu, 2014-08-21 at 15:49 +0300, Kalle Valo wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> Store the firmware registers and other relevant data to a firmware crash dump
> file and provide it to user-space via debugfs. Should help with figuring out
> why the firmware crashed.
So we just discussed Tuesday/yesterday that I'll be writing a generic
framework to provide this data to userspace, maybe you want to wait for
that.
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-08-21 13:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 12:48 [PATCH v8 0/4] ath10k: firmware crash dump Kalle Valo
2014-08-21 12:49 ` [PATCH v8 1/4] ath10k: add ath10k_pci_diag_* helpers Kalle Valo
2014-08-21 12:49 ` [PATCH v8 2/4] ath10k: provide firmware crash info via debugfs Kalle Valo
2014-08-21 13:10 ` Johannes Berg [this message]
2014-08-21 14:40 ` Kalle Valo
2014-08-22 1:19 ` Johannes Berg
2014-08-22 14:34 ` Kalle Valo
2014-08-24 9:42 ` Johannes Berg
2014-08-22 6:49 ` Michal Kazior
2014-08-25 6:28 ` Kalle Valo
2014-08-21 12:49 ` [PATCH v8 3/4] ath10k: rename ath10k_pci_hif_dump_area() to ath10k_pci_fw_crashed_dump() Kalle Valo
2014-08-21 12:49 ` [PATCH v8 4/4] ath10k: print more driver info when firmware crashes Kalle Valo
2014-08-25 8:25 ` [PATCH v8 0/4] ath10k: firmware crash dump Kalle Valo
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=1408626616.4388.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--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