summaryrefslogtreecommitdiff
path: root/drivers/pci/rom.c
diff options
context:
space:
mode:
authorAlex Chiang <achiang@hp.com>2009-01-28 14:59:18 -0700
committerJesse Barnes <jbarnes@virtuousgeek.org>2009-02-04 16:58:40 -0800
commit3419c75e15f82c3ab09bd944fddbde72c9e4b3ea (patch)
treee47c3d61d41875a35bfa4eeb504397f965050aba /drivers/pci/rom.c
parenteda58a85ec3fc05855a26654d97a2b53f0e715b9 (diff)
downloadlinux-3.10-3419c75e15f82c3ab09bd944fddbde72c9e4b3ea.tar.gz
linux-3.10-3419c75e15f82c3ab09bd944fddbde72c9e4b3ea.tar.bz2
linux-3.10-3419c75e15f82c3ab09bd944fddbde72c9e4b3ea.zip
PCI: properly clean up ASPM link state on device remove
We only want to disable ASPM when the last function is removed from the parent's device list. We determine this by checking to see if the parent's device list is completely empty. Unfortunately, we never hit that code because the parent is considered an upstream port, and never had an ASPM link_state associated with it. The early check for !link_state causes us to return early, we never discover that our device list is empty, and thus we never remove the downstream ports' link_state nodes. Instead of checking to see if the parent's device list is empty, we can check to see if we are the last device on the list, and if so, then we know that we can clean up properly. Cc: Shaohua Li <shaohua.li@intel.com> Signed-off-by: Alex Chiang <achiang@hp.com> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'drivers/pci/rom.c')
0 files changed, 0 insertions, 0 deletions