Conversation
Formality Check: Suggestions AvailableWe checked this pull request against the contribution guidelines. Here is what needs your attention:
|
43e13db to
d5043f6
Compare
|
Why in |
I put it in generic because the upstream fix is not ramips specific. It patches |
| diff --git a/drivers/net/phy/mediatek/mtk-ge.c b/drivers/net/phy/mediatek/mtk-ge.c | ||
| index 73d9b72..35600c7 100644 |
There was a problem hiding this comment.
This is raw git format-patch output, not a quilt-refreshed patch: none of the 1050 patches under target/linux/generic/ carry a diff --git header, an index line, or the trailing --/2.43.0 git footer (lines 85-86 here). Run make target/linux/refresh (with a MT7530-using target selected) and commit the result — that also regenerates hack-6.18/766-net-phy-mediatek-ge-add-LED-configuration-interface.patch,`` which patches the same file and, after this one, applies with offset 21.
Generated by Claude Code
|
Could this commit be reverted then and it would still be fixed for affected devices? |
Functionally yes on main/6.18 with this patch the EEE advertisement of the MT7530 PHY is cleared in probe() and EEE is locked off in the driver, which is earlier and stronger than the eee-broken-100tx/1000t device tree markers from b7fa9d9, so the symptoms that commit addressed are gone either way. Once the upstream fix has landed and the OpenWrt kernel bumps inherit it, the markers and this pending patch can be dropped together that looks like a cleanup for later rather than something to fold into this PR. |
d5043f6 to
b2a8f2f
Compare
openwrt-ai
left a comment
There was a problem hiding this comment.
Commit checks
- b2a8f2f "kernel: backport MT7530 broken-EEE fix from upstream" — "bound for v7.0" doesn't hold for a commit dated 8 Sep 2026; v7.0-tagged backports in this tree are January 2026 material. Name the release it actually lands in.
Generated by Claude Code
| diff --git a/drivers/net/phy/mediatek/mtk-ge.c b/drivers/net/phy/mediatek/mtk-ge.c | ||
| index 73d9b72f9d9e2..96d8ac5154e5e 100644 |
There was a problem hiding this comment.
Raw git format-patch output: none of the 165 patches in target/linux/generic/backport-6.18/ carry a diff --git or index line, quilt-refreshed patches go straight from the diffstat to --- a/.... Run make target/linux/refresh with an MT7530 target selected and commit the result; that also refreshes hack-6.18/766-net-phy-mediatek-ge-add-LED-configuration-interface.patch,`` which patches the same file and, with this patch applied first, lands its hunks 2 and 3 at offset 28.
Generated by Claude Code
| @@ -0,0 +1,101 @@ | |||
| From ccbe7540e4aad0d1c3acc249697350b93ccb8025 Mon Sep 17 00:00:00 2001 | |||
| From: Vladislav Karmanov <[email protected]> | |||
| Date: Tue, 8 Sep 2026 17:52:13 +0300 | |||
There was a problem hiding this comment.
The v7.0- prefix in the filename doesn't fit this date: the v7.0- backports in this directory are January 2026 material, and the newest prefix in tree is v7.4 on 786-01-v7.4-net-phy-add-phy_detach_internal-helper.patch`` dated 31 Aug 2026. Rename the file to the release this commit actually lands in.
Generated by Claude Code
There was a problem hiding this comment.
b2a8f2f to
b8fb444
Compare
|
Update: the fix is in Linus's tree. It was applied to netdev/net.git as ccbe7540e4aa ("net: phy: mediatek-ge: disable EEE on the MT7530 PHY") and has since been pulled into mainline - it will be part of v7.3: https://git.kernel.org/torvalds/linux/c/ccbe7540e4aa This PR now carries that upstream commit verbatim, refiled from pending-6.18 to backport-6.18 as @raenye suggested. @raenye: I kept it under generic rather than ramips/patches-6.18 because the upstream commit covers every user of this PHY driver, not just ramips/mt7621 - the MT7530 internal GE PHY is also used by boards with the standalone MT7530 IC on the mediatek target (Banana Pi R2), and the netdev review moved the fix to the PHY driver precisely to cover those too. |
| @@ -0,0 +1,101 @@ | |||
| From ccbe7540e4aad0d1c3acc249697350b93ccb8025 Mon Sep 17 00:00:00 2001 | |||
There was a problem hiding this comment.
The 800- number puts this in the "Other drivers" range, but PATCHES.md assigns 7xx to Network / PHY and 8xx to other drivers — this patches drivers/net/phy/mediatek/mtk-ge.c. Renumber into the free 7xx slots next to the other PHY backports (781-783, 786-787 are unused in this directory).
Generated by Claude Code
There was a problem hiding this comment.
Yes |
The upstream fix disabling broken EEE on the MT7530 internal GE PHY was applied to netdev/net.git (ccbe7540e4aa) and is bound for v7.3. Carry the upstream commit verbatim as a backport patch. Signed-off-by: Vladislav Karmanov <[email protected]>
b8fb444 to
c2ec0b9
Compare
|
Hi, The problem was originally observed on this kernel, and it still affects OpenWrt 25.12 on MT7621/MT7530 devices. |
Right - 25.12 (kernel 6.12) is affected too. Since the upstream commit (ccbe7540e4aa) carries a Fixes: tag for af3b4b0e59de, which is in 6.12.y, the stable process will backport it into 6.12.x once v7.3 is released, and the 25.12 branch then inherits it with the next kernel bump no extra patch needed, but that chain takes a while. So users don't have to wait, I can also open a PR against the openwrt-25.12 branch carrying the fix adapted for 6.12 (6.12 predates phy_disable_eee(), so the port clears MDIO_AN_EEE_ADV in probe()/config_init() and sets the equivalent eee_cfg/eee_broken_modes state by hand). @raenye @dangowrt: would you prefer that as a separate PR now, or the usual route - this one merged first, then a backport PR to the release branch? |
|
Usually I'd say first merge snapshot, then stable, but if the fix is different enough (i.e., more than just refreshing a patch) perhaps it's better to prepare the other PR beforehand. |
|
@work423 I am interested in the backport PR to test out locally! |
The MT7530 internal GE PHY has broken EEE: on a 2-pair cable where both ends advertise gigabit, the port loops instead of falling back to 100 Mbps, so no link and no DHCP.
Pending-6.18 patch, code identical to the netdev submission (Reviewed-by: Andrew Lunn, ETHERNET PHY LIBRARY maintainer):
https://lore.kernel.org/netdev/[email protected]/
Supersedes #22647 (per netdev review, the fix belongs in the PHY driver, not DSA). Ref: #24752.
Tested on ASUS RT-AX53U (MT7621): clean 100 Mbps WAN link + DHCP over a 2-pair cable; unpatched loops.