From: Pavel Machek <pavel@nabladev.com>
To: ovidiu.panait.rb@renesas.com
Cc: cip-dev@lists.cip-project.org, nobuhiro.iwamatsu.x90@mail.toshiba
Subject: Re: [cip-dev] [PATCH 6.1.y-cip 0/3] net: stmmac: Fix EEE-related issues
Date: Sun, 4 Jan 2026 18:29:27 +0100 [thread overview]
Message-ID: <aVqjd7TiG82mDTC5@duo.ucw.cz> (raw)
In-Reply-To: <20251229083954.3598-1-ovidiu.panait.rb@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]
Hi!
>
> When testing Ethernet on the Renesas RZ/V2H and RZ/V2N platforms with
> 6.1-cip, LPI interrupt storms and VLAN register access timeouts were
> observed.
>
> Both issues are caused by the RX clock stop feature being enabled by
> default. When EEE is active and the link is idle, the PHY stops the
> RX clock to save power. However, the stmmac hardware requires the RX
> clock to be running when accessing certain registers.
>
> More specifically, VLAN operations fail with:
>
> # ip link add link end1 name end1.5 type vlan id 5
> 15c40000.ethernet end1: Timeout accessing MAC_VLAN_Tag_Filter
> RTNETLINK answers: Device or resource busy
>
> Also, LPI interrupt storms occur because the RX clock may be stopped when
> the driver attempts to clear the pending interrupt. The interrupt is
> not cleared and keeps re-triggering until the RX clock resumes.
>
> A comprehensive overview of RX clock related issues in stmmac can be
> found in these threads:
> https://lore.kernel.org/all/20251026122905.29028-1-laurent.pinchart@ideasonboard.com/
> https://lore.kernel.org/all/Z9ySeo61VYTClIJJ@shell.armlinux.org.uk/
>
> These issues are already fixed in mainline. This series backports the
> relevant stmmac EEE fixes to 6.1-cip.
I had a minor comment here, but that should be fixed in mainline,
first, so should not block the merge.
Reviewed-by: Pavel Machek <pavel@nabladev.com>
I can apply the series if it passes testing and there are no other
comments.
Best regards,
Pavel
--
In cooperation with Nabla.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-01-04 23:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 8:39 [PATCH 6.1.y-cip 0/3] net: stmmac: Fix EEE-related issues Ovidiu Panait
2025-12-29 8:39 ` [PATCH 6.1.y-cip 1/3] net: phy: add configuration of rx clock stop mode Ovidiu Panait
2026-01-04 17:28 ` [cip-dev] " Pavel Machek
2025-12-29 8:39 ` [PATCH 6.1.y-cip 2/3] net: stmmac: Fix VLAN 0 deletion in vlan_del_hw_rx_fltr() Ovidiu Panait
2025-12-29 8:39 ` [PATCH 6.1.y-cip 3/3] net: stmmac: Disable EEE RX clock stop when VLAN is enabled Ovidiu Panait
2026-01-04 17:29 ` Pavel Machek [this message]
2026-01-07 8:17 ` [PATCH 6.1.y-cip 0/3] net: stmmac: Fix EEE-related issues nobuhiro.iwamatsu.x90
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=aVqjd7TiG82mDTC5@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=ovidiu.panait.rb@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