diff options
| author | gaolez <gaolez@codeaurora.org> | 2017-06-27 19:55:06 +0800 |
|---|---|---|
| committer | snandini <snandini@codeaurora.org> | 2017-07-05 23:36:33 -0700 |
| commit | bb4d2ce472d29a44b033c694a0e829e72ae55d3c (patch) | |
| tree | 2ed33dbdd2243cafe42f08506fa0a1ff533d4f12 | |
| parent | e8c93b519d1c31f8d726305b300ec6045482c75a (diff) | |
qcacld-2.0: fix force firmware dump incomplete
Calling function VOS_BUG after vos_force_fw_dump is the reason of
the issue, because vos_force_fw_dump will send the firmware dump
operate to work queue, and VOS_BUG will trigger crsh immediately,
so host crash will be happened before firmware dump finish.
For vos_force_fw_dump, it will trigger subsystem_restart_dev after
dump firmware finished, so delete VOS_BUG after vos_force_fw_dump.
Change-Id: I0d779e90ce0f50dc033f0efc30f3e724a4b797de
CRs-fixed: 2067704
| -rw-r--r-- | CORE/SERVICES/WMA/wma.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/CORE/SERVICES/WMA/wma.c b/CORE/SERVICES/WMA/wma.c index 116e8c924880..d7827a602dfe 100644 --- a/CORE/SERVICES/WMA/wma.c +++ b/CORE/SERVICES/WMA/wma.c @@ -24504,11 +24504,9 @@ int wma_enable_wow_in_fw(WMA_HANDLE handle, int runtime_pm) vos_trigger_recovery(false); } else { vos_force_fw_dump(); - VOS_BUG(0); } #else vos_force_fw_dump(); - VOS_BUG(0); #endif } else { WMA_LOGE("%s: LOGP is in progress, ignore!", __func__); |