summaryrefslogtreecommitdiff
path: root/net/l2tp/l2tp_ppp.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2018-06-05 15:50:18 +0300
committerDavid S. Miller <davem@davemloft.net>2018-06-05 15:50:18 +0300
commit7a723099be325f6c5edd25c775b672a056907f75 (patch)
tree9a3188f34ac7db2ee7c749a80fc6beb40060950c /net/l2tp/l2tp_ppp.c
parent7d840a606515b04dfb4f13d1abb86dd59163799c (diff)
parent9107c05e2e55c1c7abd02ab38f7694e0da08b643 (diff)
downloadlinux-7a723099be325f6c5edd25c775b672a056907f75.tar.xz
Merge branch 'net-phy-improve-PM-handling-of-PHY-MDIO'
Heiner Kallweit says: ==================== net: phy: improve PM handling of PHY/MDIO Current implementation of MDIO bus PM ops doesn't actually implement bus-specific PM ops but just calls PM ops defined on a device level what doesn't seem to be fully in line with the core PM model. When looking e.g. at __device_suspend() the PM core looks for PM ops of a device in a specific order: 1. device PM domain 2. device type 3. device class 4. device bus I think it has good reason that there's no PM ops on device level. The situation can be improved by modeling PHY's as device type of a MDIO device. If for some other type of MDIO device PM ops are needed, it could be modeled as struct device_type as well. ==================== Tested-by: Andrew Lunn <andrew@lunn.ch> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/l2tp/l2tp_ppp.c')
0 files changed, 0 insertions, 0 deletions