From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"biju.das.au" <biju.das.au@gmail.com>
Subject: Re: [PATCH net-next] net: stmmac: dwmac-renesas-gbeth: Add PM suspend/resume callbacks
Date: Sun, 6 Jul 2025 11:10:44 +0100 [thread overview]
Message-ID: <aGpLpLDPdcPByC7j@shell.armlinux.org.uk> (raw)
In-Reply-To: <TY3PR01MB113467D8E13143E412B119270864CA@TY3PR01MB11346.jpnprd01.prod.outlook.com>
On Sun, Jul 06, 2025 at 09:55:28AM +0000, Biju Das wrote:
> Just adding some logs:
> Currently PHY resume is called twice
> [ 35.754933] kszphy_resume+0x3c/0xf0
> [ 35.754940] phy_resume+0x3c/0x74
> [ 35.754949] phylink_prepare_resume+0x58/0xa0
> [ 35.754957] stmmac_resume+0x90/0x2a0
> [ 35.771296] stmmac_pltfr_resume+0x3c/0x4c
>
> and
>
> [ 35.771258] kszphy_resume+0x3c/0xf0
> [ 35.771263] __phy_resume+0x28/0x54
> [ 35.771270] phy_start+0x7c/0xb4
> [ 35.771275] phylink_start+0xb8/0x210
> [ 35.771282] phylink_resume+0x7c/0xc4
> [ 35.771288] stmmac_resume+0x1ec/0x2a0
> [ 35.771296] stmmac_pltfr_resume+0x3c/0x4c
This shouldn't be a problem. Phylib will do this, and PHY drivers are
expected to cope.
For example, on non-MAC managed PM PHYs, mdio_bus_phy_resume() will
call phy_init_hw() followed by phy_resume(). If a MAC subsequently is
brought up, phy_start() will be called, which will also call
__phy_resume().
If this is upsetting the KSZ PHY, then the KSZ PHY driver needs fixing.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-07-06 10:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-05 17:03 [PATCH net-next] net: stmmac: dwmac-renesas-gbeth: Add PM suspend/resume callbacks Biju Das
2025-07-05 19:31 ` Russell King (Oracle)
2025-07-05 20:26 ` Biju Das
2025-07-06 8:45 ` Biju Das
2025-07-06 9:55 ` Biju Das
2025-07-06 10:10 ` Russell King (Oracle) [this message]
2025-07-06 14:06 ` Biju Das
2025-07-06 10:06 ` Russell King (Oracle)
2025-07-06 10:17 ` Biju Das
2025-07-16 18:19 ` Biju Das
2025-07-16 19:36 ` Biju Das
2025-07-16 19:26 ` Lad, Prabhakar
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=aGpLpLDPdcPByC7j@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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;
as well as URLs for NNTP newsgroup(s).