summaryrefslogtreecommitdiffstats
path: root/drivers/firewire/Kconfig
diff options
context:
space:
mode:
authorReinette Chatre <reinette.chatre@intel.com>2010-02-03 09:38:59 -0800
committerGreg Kroah-Hartman <gregkh@suse.de>2010-07-05 11:16:06 -0700
commit5bd90999347524d2b525d011a68b70837a922879 (patch)
treecc62306d7395ee3824fedf582250eadd677f95a2 /drivers/firewire/Kconfig
parent5ff290f1c541bb4d4c8df68b31378d6e031eeba1 (diff)
downloadkernel-crypto-5bd90999347524d2b525d011a68b70837a922879.tar.gz
kernel-crypto-5bd90999347524d2b525d011a68b70837a922879.tar.xz
kernel-crypto-5bd90999347524d2b525d011a68b70837a922879.zip
iwlwifi: reset card during probe
commit 4843b5a731b31916d100cfc5ba4d03ae78462ed9 upstream. To ensure that card is in a sane state during probe we add a reset call. This change was prompted by users of kdump who was not able to bring up the wireless driver in the kdump kernel. The problem here was that the primary kernel, which is not running at the time, left the wireless card up and running. When the kdump kernel starts it is thus possible to immediately receive interrupts from firmware after registering interrupt, but without being ready to deal with interrupts from firmware yet. Reported-by: Stanislaw Gruszka <sgruszka@redhat.com> Signed-off-by: Reinette Chatre <reinette.chatre@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/firewire/Kconfig')
0 files changed, 0 insertions, 0 deletions