| commit | d5aebc77b47f9e0a2b465fbcf77bde033a231c24 | |
| author | Ben Greear <greearb@candelatech.com> | |
| Wed, 10 Sep 2014 15:59:28 +0000 (10 18:59 +0300) | ||
| committer | Kalle Valo <kvalo@qca.qualcomm.com> | |
| Thu, 11 Sep 2014 20:44:17 +0000 (11 23:44 +0300) | ||
| tree | aa35867b9b5efe1419f093bc10828ffb437c4a30 | treesnapshot (tar.gz zip) |
| parent | 43d2a30fa80166243498fc6b8c841828ce52fcc1 | commitdiff |
ath10k: support firmware crash-by-assert
10.1 firmware does not have an official way to
cause assert on purpose, but it can be done with
carefully crafted WMI command. This is a different
kind of crash from the 'hard' crash, which is
a bad memory dereference.
Different crashes decode in different manners, so
this will help the crash-report testing as well as
offer better ways to test firmware failure and
recovery.
kvalo: move the wmi command creation to debug.c, modify
the info print
Signed-off-by: Ben Greear <greearb@candelatech.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
10.1 firmware does not have an official way to
cause assert on purpose, but it can be done with
carefully crafted WMI command. This is a different
kind of crash from the 'hard' crash, which is
a bad memory dereference.
Different crashes decode in different manners, so
this will help the crash-report testing as well as
offer better ways to test firmware failure and
recovery.
kvalo: move the wmi command creation to debug.c, modify
the info print
Signed-off-by: Ben Greear <greearb@candelatech.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
| drivers/net/wireless/ath/ath10k/debug.c | diffblobblamehistory |