diff options
author | 2016-06-24 21:23:48 +0300 | |
---|---|---|
committer | 2016-06-28 08:57:18 -0400 | |
commit | a01d7baa1f2e291b1b3d82d57ae41d2fd9d438c3 (patch) | |
tree | 7da5dd65229340e279d669563246974dfe4e69bf /net/tipc | |
parent | drivers: net: davinci_mdio: remove pm runtime calls from suspend callbacks (diff) | |
download | wireguard-linux-a01d7baa1f2e291b1b3d82d57ae41d2fd9d438c3.tar.xz wireguard-linux-a01d7baa1f2e291b1b3d82d57ae41d2fd9d438c3.zip |
drivers: net: davinci_mdio: drop suspended and lock fields from mdio_data
It's not expected Davinci MDIO to be accessible after its suspend
callbacks have been called:
- all consumers of Davinci MDIO will stop/disconnect phys at Device
suspend stage;
- all phys are expected to be suspned already by PHY/MDIO core;
- MDIO locking is done by MDIO Bus code.
Hence, it's safe to drop "suspended" and "lock" fields from mdio_data.
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/tipc')
0 files changed, 0 insertions, 0 deletions