MT7621 SoC Traffic Won't Flow on RGMII2 Bus/2nd GMAC

[Arınç ÜNAL]

Hi all,

The company I currently work for has got an Ralink mt7621a board with an 
external phy connected. It's a Realtek rtl8367s switch.
I've been running gregkh/staging staging-next & netdev/net-next master 
branches with Sergio's "clk: ralink: make system controller a reset 
provider" v8 patch series.

We don't have traffic flow on the RGMII2 bus which is shared by the 2nd 
GMAC of the SoC, MT7530's GMAC5 and an external phy (rtl switch in our 
case).

According to Documentation/devicetree/bindings/net/dsa/mt7530.txt, I can 
either configure the external phy to connect to the second GMAC of the 
mt7621 SoC or to MT7530's GMAC5 to create a cascade.

None of the documented configurations work:
External phy <-> 2nd GMAC
External phy <-> MT7530's GMAC5

The external switch works with Mediatek SDK ethernet driver on External 
phy <-> 2nd GMAC mode.

I suspect there is a problem with the mtk_eth_soc driver on upstream.
Same issue on 5.10 (OpenWrt Master) and 4.14 (OpenWrt 19.07)

The board's RTL8367S schematics is in the attachments.

Dumbed down wiring scheme:
                             CPU
                      ┌───────────────┐
                      │ GMAC0 | GMAC1 │
                      └───┼───────┼───┘
                          │       │
             ┌────────────┼┐      │
      MT7530 │0 1 2 3 4 5 6│      │
             └─────────────┘      │
                          ┌───────┘
             ┌────────────┼┐
    RTL8367S │0 1 2 3 4 6 7│
             └┼─┼─┼─┼─┼────┘
      ┌───────┘ │ │ │ └───────┐
      │     ┌───┘ │ └───┐     │
      │     │     │     │     │
      │     │     │     │     │
  ┌───┼─────┼─────┼─────┼─────┼───┐
  │ sw1p0 sw1p1 sw1p2 sw1p3 sw1p4 │
  └───────────────────────────────┘

Cheers.
Arınç
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Xeront_7531_8367.pdf
Type: application/pdf
Size: 361521 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-mediatek/attachments/20220122/0f7864f6/attachment-0001.pdf>