From: Greg KH <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: linux-stable <stable@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>
Subject: Re: Stable request: net: stmmac: resume rx clocking
Date: Mon, 28 Apr 2025 13:49:32 +0200 [thread overview]
Message-ID: <2025042826-radiantly-rack-2542@gregkh> (raw)
In-Reply-To: <ec5cf6b5-a32e-4f98-a591-9cb13a9202e9@nvidia.com>
On Thu, Apr 24, 2025 at 05:56:53PM +0100, Jon Hunter wrote:
> Hi Greg, Sasha,
>
> Updates to the stmmac networking driver in Linux v6.14 exposed some issues
> with resuming the driver on platforms such as the Tegra186 Jetson TX2 board.
> This is why the suspend test has been failing on this platform for the
> linux-6.14.y updates ...
>
> Test failures: tegra186-p2771-0000: pm-system-suspend.sh
>
> Russell has provided some fixes for this that are now in the mainline and so
> I would like to integrate the following changes to linux-6.14.y ...
>
> f732549eb303 net: stmmac: simplify phylink_suspend() and
> phylink_resume() calls
> 367f1854d442 net: phylink: add phylink_prepare_resume()
> ef43e5132895 net: stmmac: address non-LPI resume failures properly
> 366aeeba7908 net: stmmac: socfpga: remove phy_resume() call
> ddf4bd3f7384 net: phylink: add functions to block/unblock rx clock stop
> dd557266cf5f net: stmmac: block PHY RXC clock-stop
>
> I had a quick look to see if we can backport to linux-6.12.y but looks like
> we need more commits and so for now just target linux-6.14.y.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2025-04-28 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 16:56 Stable request: net: stmmac: resume rx clocking Jon Hunter
2025-04-28 11:49 ` Greg KH [this message]
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=2025042826-radiantly-rack-2542@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=stable@vger.kernel.org \
/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