diff options
author | Bruce Allan | 2011-03-24 04:09:03 +0100 |
---|---|---|
committer | Jeff Kirsher | 2011-04-14 04:19:22 +0200 |
commit | 78cd29d5a92ae5067377ad42089f2c8781312f4a (patch) | |
tree | fb9845f2fdb6c28890478c7fa8fbcfec79e4543d /drivers/net/ixgbe/ixgbe_dcb_nl.c | |
parent | e1000e: fix stats locking in e1000_watchdog_task (diff) | |
download | kernel-qcow2-linux-78cd29d5a92ae5067377ad42089f2c8781312f4a.tar.gz kernel-qcow2-linux-78cd29d5a92ae5067377ad42089f2c8781312f4a.tar.xz kernel-qcow2-linux-78cd29d5a92ae5067377ad42089f2c8781312f4a.zip |
e1000e: If ASPM L0s needs to be disabled, do it prior to enabling device
Based on a patch from Naga Chumbalkar <nagananda.chumbalkar@hp.com>:
If ASPM L0s needs to be disabled due to HW errata, do it prior to
"enabling" the device. This way if the kernel ever defaults its
aspm_policy to POLICY_POWERSAVE, then the e1000e driver will get a
chance to disable ASPM on the misbehaving device *prior* to calling
pci_enable_device_mem(). This will be useful in situations
where the BIOS indicates ASPM support on the server by clearing the
ACPI FADT "ASPM Controls" bit.
Note:
The kernel (2.6.38) currently uses the BIOS "default" as its aspm_policy.
However, Linux distros can diverge from that and set the default to
"powersave".
v2: o cleanup namespace pollution of e1000e_disable_aspm(),
o fix type and initialization of the new aspm_disable_flag in a few
functions, and
o redefine FLAG2_DISABLE_ASPM_L0S to the first unused bit in
adapter->flags2.
Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
Cc: Naga Chumbalkar <nagananda.chumbalkar@hp.com>
Tested-by: Aaron Brown <aaron.f.brown@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'drivers/net/ixgbe/ixgbe_dcb_nl.c')
0 files changed, 0 insertions, 0 deletions