igb: No longer rely on APME to determine WoL settings
authorMatthew Vick <matthew.vick@intel.com>
Fri, 9 Nov 2012 05:49:54 +0000 (05:49 +0000)
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>
Thu, 22 Nov 2012 10:00:58 +0000 (02:00 -0800)
commit63d4a8f963fce8fe5d8ba3d5eba34d7d7ca6f82b
tree34d71b51d5abcfa21be055245b6e8292b1aedb83
parent3e961a06a0d509d9f7cddc8240431d25f6dcd51f
igb: No longer rely on APME to determine WoL settings

Historically, we've been using the APME bit to determine whether a device
supports wake on a given port or not. However, this bit specifies the
default wake setting, rather than the wake support. Change the behavior so
that we use a flag to keep the capabilities separate from the enablement
while meeting customer requirements.

Signed-off-by: Matthew Vick <matthew.vick@intel.com>
Tested-by: Aaron Brown <aaron.f.brown@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
drivers/net/ethernet/intel/igb/igb.h
drivers/net/ethernet/intel/igb/igb_ethtool.c
drivers/net/ethernet/intel/igb/igb_main.c