[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZZfPOky2p/ZJMKCQ@shell.armlinux.org.uk>
Date: Fri, 5 Jan 2024 09:43:22 +0000
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: Claudiu <claudiu.beznea@...on.dev>
Cc: andrew@...n.ch, hkallweit1@...il.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
yuiko.oshino@...rochip.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
Subject: Re: [PATCH net] net: phy: micrel: populate .soft_reset for KSZ9131
On Fri, Jan 05, 2024 at 10:52:42AM +0200, Claudiu wrote:
> The order of PHY-related operations in ravb_open() is as follows:
> ravb_open() ->
> ravb_phy_start() ->
> ravb_phy_init() ->
> of_phy_connect() ->
> phy_connect_direct() ->
> phy_attach_direct() ->
> phy_init_hw() ->
> phydev->drv->soft_reset()
> phydev->drv->config_init()
> phydev->drv->config_intr()
> phy_resume()
> kszphy_resume()
>
> The order of PHY-related operations in ravb_close is as follows:
> ravb_close() ->
> phy_stop() ->
> phy_suspend() ->
> kszphy_suspend() ->
> genphy_suspend()
> // set BMCR_PDOWN bit in MII_BMCR
Andrew,
This looks wrong to me - shouldn't we be resuming the PHY before
attempting to configure it?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists