git.baikalelectronics.ru Git - kernel.git/commit

]> git.baikalelectronics.ru Git - kernel.git/commit

author	Emmanuel Grumbach <emmanuel.grumbach@intel.com>
	Thu, 29 Jan 2015 12:58:20 +0000 (14:58 +0200)
committer	Emmanuel Grumbach <emmanuel.grumbach@intel.com>
	Mon, 2 Mar 2015 06:20:28 +0000 (08:20 +0200)
commit	72f4b52f92cd0afa8f8bdf63a6deaea63911654f
tree	69869fec6604ece7ef73c1a6c1395231d7c8a3dd	tree \| snapshot
parent	40508f0636bf4e8c89a6722729ed0e77c18d3253	commit \| diff

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>

Linux Kernel Source Tree.

RSS Atom

drivers/net/wireless/iwlwifi/iwl-fw-error-dump.h		diff \| blob \| history
drivers/net/wireless/iwlwifi/mvm/debugfs.c		diff \| blob \| history
drivers/net/wireless/iwlwifi/mvm/fw.c		diff \| blob \| history
drivers/net/wireless/iwlwifi/mvm/mac80211.c		diff \| blob \| history
drivers/net/wireless/iwlwifi/mvm/mvm.h		diff \| blob \| history
drivers/net/wireless/iwlwifi/mvm/ops.c		diff \| blob \| history