ath10k: support dev_coredump for crash dump

Kalle Valo kvalo at qca.qualcomm.com
Fri Dec 30 01:14:34 PST 2016


Kalle Valo <kvalo at qca.qualcomm.com> wrote:
> From: Arun Khandavalli <akhandav at qti.qualcomm.com>
> 
> Whenever firmware crashes, and both CONFIG_ATH10K_DEBUGFS and
> CONFIG_ALLOW_DEV_COREDUMP are enabled, dump information about the crash via a
> devcoredump device. Dump can be read from userspace for further analysis from:
> 
> /sys/class/devcoredump/devcd*/data
> 
> As until now we have provided the firmware crash dump file via fw_crash_dump
> debugfs keep it still available but deprecate and a warning print that the user
> should switch to using dev_coredump.
> 
> Future improvement would be not to depend on CONFIG_ATH10K_DEBUGFS, as there
> might be systems which want to get the firmware crash dump but not enable
> debugfs. How to handle memory consumption is also something which needs to be
> taken into account.
> 
> Signed-off-by: Arun Khandavalli <akhandav at qti.qualcomm.com>
> [kvalo at qca.qualcomm.com: rebase, fixes, improve commit log]
> Signed-off-by: Kalle Valo <kvalo at qca.qualcomm.com>

Patch applied to ath-next branch of ath.git, thanks.

727000e6af34 ath10k: support dev_coredump for crash dump

-- 
https://patchwork.kernel.org/patch/9482989/

Documentation about submitting wireless patches and checking status
from patchwork:

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches




More information about the ath10k mailing list