summaryrefslogtreecommitdiff
path: root/Kconfig
diff options
context:
space:
mode:
authorLendacky, Thomas <Thomas.Lendacky@amd.com>2015-02-25 13:50:12 -0600
committerDavid S. Miller <davem@davemloft.net>2015-02-27 17:13:02 -0500
commitc30e76a728beb5bbfff0ddeb573e28927853d4b8 (patch)
treecc27ab027899a71951ad4d1e26ffe2d5a84011fe /Kconfig
parent7488c3e3d8384e6a3d71c6a05645b3db8d82d275 (diff)
downloadlwn-c30e76a728beb5bbfff0ddeb573e28927853d4b8.tar.gz
lwn-c30e76a728beb5bbfff0ddeb573e28927853d4b8.zip
amd-xgbe: Request IRQs only after driver is fully setup
It is possible that the hardware may not have been properly shutdown before this driver gets control, through use by firmware, for example. Until the driver is loaded, interrupts associated with the hardware could go pending. When the IRQs are requested napi support has not been initialized yet, but the ISR will get control and schedule napi processing resulting in a kernel panic because the poll routine has not been set. Adjust the code so that the driver is fully ready to handle and process interrupts as soon as the IRQs are requested. This involves requesting and freeing IRQs during start and stop processing and ordering the napi add and delete calls appropriately. Also adjust the powerup and powerdown routines to match the start and stop routines in regards to the ordering of tasks, including napi related calls. Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions