diff options
| author | Emmanuel Grumbach <emmanuel.grumbach@intel.com> | 2015-01-29 14:58:20 +0200 |
|---|---|---|
| committer | Emmanuel Grumbach <emmanuel.grumbach@intel.com> | 2015-03-02 08:20:28 +0200 |
| commit | b6eaa45aa18bf010fd54cdac0e3007dfdd7f3f8a (patch) | |
| tree | 69869fec6604ece7ef73c1a6c1395231d7c8a3dd /drivers/net/wireless/iwlwifi/mvm/debugfs.c | |
| parent | d2709ad723ff2ae22013978ed6ec29cf1b9b8332 (diff) | |
| download | blackbird-obmc-linux-b6eaa45aa18bf010fd54cdac0e3007dfdd7f3f8a.tar.gz blackbird-obmc-linux-b6eaa45aa18bf010fd54cdac0e3007dfdd7f3f8a.zip | |
iwlwifi: mvm: add the cause of the firmware dump in the dump
Now that the firmware dump can be triggered by events in
the code and not only the user or an firmware ASSERT, we
need a way to know why the firmware dump was triggered.
Add a section in the dump file for that.
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Diffstat (limited to 'drivers/net/wireless/iwlwifi/mvm/debugfs.c')
| -rw-r--r-- | drivers/net/wireless/iwlwifi/mvm/debugfs.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/wireless/iwlwifi/mvm/debugfs.c b/drivers/net/wireless/iwlwifi/mvm/debugfs.c index f890d5e4673f..8cbe77dc1dbb 100644 --- a/drivers/net/wireless/iwlwifi/mvm/debugfs.c +++ b/drivers/net/wireless/iwlwifi/mvm/debugfs.c @@ -985,7 +985,7 @@ static ssize_t iwl_dbgfs_fw_dbg_collect_write(struct iwl_mvm *mvm, if (ret) return ret; - iwl_mvm_fw_dbg_collect(mvm, FW_DBG_TRIGGER_USER, 0); + iwl_mvm_fw_dbg_collect(mvm, FW_DBG_TRIGGER_USER, NULL, 0, 0); iwl_mvm_unref(mvm, IWL_MVM_REF_PRPH_WRITE); |
