netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: "Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
	"DENG Qingfang" <dqfext@gmail.com>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	"John Crispin" <john@phrozen.org>,
	"Siddhant Gupta" <siddhantgupta416@gmail.com>,
	"Ilya Lipnitskiy" <ilya.lipnitskiy@gmail.com>,
	"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
	"Felix Fietkau" <nbd@nbd.name>,
	"Sean Wang" <sean.wang@mediatek.com>,
	"Mark Lee" <Mark-MC.Lee@mediatek.com>,
	"Russell King" <linux@armlinux.org.uk>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"David Miller" <davem@davemloft.net>,
	"René van Dorst" <opensource@vdorst.com>
Cc: linux-mediatek@lists.infradead.org, netdev@vger.kernel.org,
	linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
	openwrt-devel@lists.openwrt.org, erkin.bozoglu@xeront.com
Subject: MT7621 SoC Traffic Won't Flow on RGMII2 Bus/2nd GMAC
Date: Sat, 22 Jan 2022 21:01:31 +0300	[thread overview]
Message-ID: <83a35aa3-6cb8-2bc4-2ff4-64278bbcd8c8@arinc9.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2200 bytes --]

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ç

[-- Attachment #2: Xeront_7531_8367.pdf --]
[-- Type: application/pdf, Size: 361521 bytes --]

             reply	other threads:[~2022-01-22 18:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22 18:01 Arınç ÜNAL [this message]
2022-01-23  6:51 ` MT7621 SoC Traffic Won't Flow on RGMII2 Bus/2nd GMAC DENG Qingfang
2022-01-23  8:33   ` Arınç ÜNAL
2022-01-23 15:26     ` Andrew Lunn
2022-01-23 17:48       ` Arınç ÜNAL
2022-01-24 17:13       ` Florian Fainelli
2022-01-24 17:26         ` Russell King (Oracle)
2022-01-24 17:34           ` Florian Fainelli

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=83a35aa3-6cb8-2bc4-2ff4-64278bbcd8c8@arinc9.com \
    --to=arinc.unal@arinc9.com \
    --cc=Mark-MC.Lee@mediatek.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dqfext@gmail.com \
    --cc=erkin.bozoglu@xeront.com \
    --cc=ilya.lipnitskiy@gmail.com \
    --cc=john@phrozen.org \
    --cc=kuba@kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=luizluca@gmail.com \
    --cc=matthias.bgg@gmail.com \
    --cc=nbd@nbd.name \
    --cc=netdev@vger.kernel.org \
    --cc=opensource@vdorst.com \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=sean.wang@mediatek.com \
    --cc=sergio.paracuellos@gmail.com \
    --cc=siddhantgupta416@gmail.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;
as well as URLs for NNTP newsgroup(s).