From: patchwork-bot+netdevbpf@kernel.org
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, wei.fang@nxp.com,
xiaoning.wang@nxp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: phy: realtek: restore RTL8211F RGMII delays on resume
Date: Tue, 20 Oct 2026 20:10:16 +0000 [thread overview]
Message-ID: <179252701602.186787.14998467033083522856.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261015045001.83986-1-kmehltretter@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 15 Oct 2026 06:50:01 +0200 you wrote:
> RTL8211F and RTL8211F-VD both use rtl8211f_config_rgmii_delay() during
> initialization and share rtl821x_resume(). The RTL8211F-VD loses its
> RGMII TX and RX delay enable bits across a software power-down, but the
> shared resume path only clears BMCR_PDOWN and waits for the receive clock
> to stabilize.
>
> On a BeagleV Ahead configured for rgmii-id, carrier and the negotiated
> speed return after an interface close/open, but the receive path does not
> work. At 100 Mbit/s no frames were received. At 1000 Mbit/s all 11
> observed frames had CRC errors.
>
> [...]
Here is the summary with links:
- [net,v2] net: phy: realtek: restore RTL8211F RGMII delays on resume
https://git.kernel.org/netdev/net-next/c/20c0c6773624
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-20 20:10 UTC|newest]
Thread overview: 3+ 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
2026-10-20 20:10 ` patchwork-bot+netdevbpf [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=179252701602.186787.14998467033083522856.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kmehltretter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox