[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1ee9ee17-6582-4cb1-9a17-072be7d2b2c0@lunn.ch>
Date: Thu, 2 May 2024 18:37:07 +0200
From: Andrew Lunn <andrew@...n.ch>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Raju Lakkaraju <Raju.Lakkaraju@...rochip.com>, netdev@...r.kernel.org,
lxu@...linear.com, hkallweit1@...il.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
linux-kernel@...r.kernel.org, UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH net-next] net: phy: add wol config options in phy device
> It would be good to hear exactly why its necessary for phylib to track
> this state, and why the PHY isn't retaining it.
I _think_ it is a hardware reset. The call path is probably:
mdio_bus_phy_resume():
phy_init_hw():
phy_device_reset()
mdio_device_reset()
But it would be good to get this confirmed.
Andrew
Powered by blists - more mailing lists