From: Karl Mehltretter <kmehltretter@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Wei Fang <wei.fang@nxp.com>,
Clark Wang <xiaoning.wang@nxp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: phy: realtek: restore RTL8211F RGMII delays on resume
Date: Fri, 16 Oct 2026 13:16:32 +0200 [thread overview]
Message-ID: <atIHEinHKXsD-0z8@gmail.com> (raw)
In-Reply-To: <20261015045001.83986-1-kmehltretter@gmail.com>
On Thu, Oct 15, 2026 at 06:50:01AM +0100, Karl Mehltretter wrote:
> Reapply the RGMII delay configuration after the existing resume delay.
>
> Tested on a BeagleV Ahead with an RTL8211F-VD at 100 and 1000 Mbit/s,
> including close/open without a link partner.
>
> Fixes: bb726b753f75 ("net: phy: realtek: add support for RTL8211F(D)(I)-VD-CG")
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
> ---
> v2:
> - Move the shared RTL8211F/RTL8211F-VD resume-path explanation earlier.
> - Add Andrew's Reviewed-by.
>
> v1: https://lore.kernel.org/netdev/20261014033659.95196-1-kmehltretter@gmail.com/
>
Now Sashiko found a possible clock reference leak in the resume error
path:
https://sashiko.dev/#/patchset/20261015045001.83986-1-kmehltretter@gmail.com
I'll take a look.
Karl
prev parent reply other threads:[~2026-10-16 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 4:50 [PATCH net v2] net: phy: realtek: restore RTL8211F RGMII delays on resume Karl Mehltretter
2026-10-16 11:16 ` Karl Mehltretter [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=atIHEinHKXsD-0z8@gmail.com \
--to=kmehltretter@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--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=pabeni@redhat.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.