]> asedeno.scripts.mit.edu Git - linux.git/commit
iwlwifi: differentiate between alive timeout and alive flow failure
authorShahar S Matityahu <shahar.s.matityahu@intel.com>
Thu, 22 Nov 2018 07:12:08 +0000 (09:12 +0200)
committerLuca Coelho <luciano.coelho@intel.com>
Mon, 4 Feb 2019 10:27:18 +0000 (12:27 +0200)
commit67b8261c49a050dccd776f13b28816dcea226d0c
tree8b878c0f1ad371c645345fb536699d3affd283b1
parent74a102521208554e0daf52b0aeb742c066ad1e34
iwlwifi: differentiate between alive timeout and alive flow failure

There are two cases that can cause the alive flow to fail,
an assert or a timeout.
Currently we mask any incoming asserts when we wait for alive.

Solve this by differentiating between the two cases:
1. Let the regular error handling to handle a received assert
2. Do a dump collection in the case of a timeout

Signed-off-by: Shahar S Matityahu <shahar.s.matityahu@intel.com>
Fixes: f38efdb29389 ("iwlwifi: add dump collection in case alive flow fails")
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
drivers/net/wireless/intel/iwlwifi/fw/dbg.c
drivers/net/wireless/intel/iwlwifi/fw/dbg.h
drivers/net/wireless/intel/iwlwifi/fw/error-dump.h
drivers/net/wireless/intel/iwlwifi/fw/runtime.h
drivers/net/wireless/intel/iwlwifi/mvm/fw.c
drivers/net/wireless/intel/iwlwifi/mvm/ops.c