summaryrefslogtreecommitdiffstats
path: root/drivers/net/wimax
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2018-09-26 20:04:11 -0700
committerDavid S. Miller <davem@davemloft.net>2018-09-26 20:04:11 -0700
commit30ed48719282aecf6728f6777fefe8440bf6ed5a (patch)
treec36973bf5980fc937c213c93f6b773068ffbc21e /drivers/net/wimax
parentd31d1d03aa909aa6257d9d581eb0eb5d0ed366e2 (diff)
parent93f41e67dc8ff0fd987120a6ef2717f21462c534 (diff)
downloadlinux-30ed48719282aecf6728f6777fefe8440bf6ed5a.tar.bz2
Merge branch 'net-phy-fix-WoL-handling-when-suspending-the-PHY'
Heiner Kallweit says: ==================== net: phy: fix WoL handling when suspending the PHY phy_suspend doesn't always recognize that WoL is enabled and therefore suspends the PHY when it should not. First idea to address the issue was to reuse checks used in mdio_bus_phy_may_suspend which check whether relevant devices are wakeup-enabled. Florian raised some concerns because drivers may enable wakeup even if WoL isn't enabled (e.g. certain USB network drivers). The new approach focuses on reducing the risk to break existing stuff. We add a flag wol_enabled to struct net_device which is set in ethtool_set_wol(). Then this flag is checked in phy_suspend(). This doesn't cover 100% of the cases yet (e.g. if WoL is enabled w/o explicit configuration), but it covers the most relevant cases with very little risk of regressions. v2: - Fix a typo ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/wimax')
0 files changed, 0 insertions, 0 deletions