From: <Claudiu.Beznea@microchip.com>
To: <olteanv@gmail.com>
Cc: <Nicolas.Ferre@microchip.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<linux@armlinux.org.uk>, <andrew@lunn.ch>, <hkallweit1@gmail.com>,
<Sergiu.Moga@microchip.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] net: phylink: init phydev on phylink_resume()
Date: Mon, 12 Dec 2022 15:20:11 +0000 [thread overview]
Message-ID: <d22c8ec9-49d3-3af6-cf0e-14558cbfc17b@microchip.com> (raw)
In-Reply-To: <20221212135408.j23agcjrikiucq4a@skbuf>
Hi, Vladimir,
On 12.12.2022 15:54, Vladimir Oltean wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Hi Claudiu,
>
> On Mon, Dec 12, 2022 at 01:28:44PM +0200, Claudiu Beznea wrote:
>> There are scenarios where PHY power is cut off on system suspend.
>> There are also MAC drivers which handles themselves the PHY on
>> suspend/resume path. For such drivers the
>> struct phy_device::mac_managed_phy is set to true and thus the
>> mdio_bus_phy_suspend()/mdio_bus_phy_resume() wouldn't do the
>> proper PHY suspend/resume. For such scenarios call phy_init_hw()
>> from phylink_resume().
>>
>> Suggested-by: Russell King (Oracle) <linux@armlinux.org.uk>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
>> ---
>>
>> Hi, Russel,
>>
>> I let phy_init_hw() to execute for all devices. I can restrict it only
>> for PHYs that has struct phy_device::mac_managed_phy = true.
>>
>> Please let me know what you think.
>>
>> Thank you,
>> Claudiu Beznea
>>
>>
>> drivers/net/phy/phylink.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/drivers/net/phy/phylink.c b/drivers/net/phy/phylink.c
>> index 09cc65c0da93..6003c329638e 100644
>> --- a/drivers/net/phy/phylink.c
>> +++ b/drivers/net/phy/phylink.c
>> @@ -2031,6 +2031,12 @@ void phylink_resume(struct phylink *pl)
>> {
>> ASSERT_RTNL();
>>
>> + if (pl->phydev) {
>> + int ret = phy_init_hw(pl->phydev);
>> + if (ret)
>> + return;
>> + }
>> +
>
> If the config_init() method of the driver does things such as this:
>
> phydev->mdix_ctrl = ETH_TP_MDI_AUTO;
>
> like for example the marvell10g.c driver, won't a user-configured manual
> MDI setting get overwritten after a suspend/resume cycle?
I'm not fully sure about it. I have to look further though the code.
At the same time phy_init_hw() is called also on mdio_bus_phy_resume().
Thank you,
Claudiu Beznea
>
>> if (test_bit(PHYLINK_DISABLE_MAC_WOL, &pl->phylink_disable_state)) {
>> /* Wake-on-Lan enabled, MAC handling */
>>
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2022-12-12 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 11:28 [PATCH v2 0/2] net: macb: fix connectivity after resume Claudiu Beznea
2022-12-12 11:28 ` [PATCH v2 1/2] net: phylink: init phydev on phylink_resume() Claudiu Beznea
2022-12-12 12:47 ` Russell King (Oracle)
2022-12-12 13:26 ` Claudiu.Beznea
2022-12-12 14:24 ` Russell King (Oracle)
2022-12-12 14:46 ` Claudiu.Beznea
2022-12-12 13:54 ` Vladimir Oltean
2022-12-12 15:20 ` Claudiu.Beznea [this message]
2022-12-12 11:28 ` [PATCH v2 2/2] net: macb: use phylink_suspend()/phylink_resume() Claudiu Beznea
2022-12-14 1:39 ` [PATCH v2 0/2] net: macb: fix connectivity after resume Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d22c8ec9-49d3-3af6-cf0e-14558cbfc17b@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Sergiu.Moga@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox