[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dc66ab0e-1c63-4a57-98a5-a440d97d13f7@lunn.ch>
Date: Fri, 29 Dec 2023 22:43:48 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Jagan Teki <jagan@...rulasolutions.com>
Cc: Vladimir Oltean <olteanv@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
"Andrew F. Davis" <afd@...com>,
Florian Fainelli <f.fainelli@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org,
Michael Nazzareno Trimarchi <michael@...rulasolutions.com>,
Ioana Ciornei <ioana.ciornei@....com>,
Shawn Guo <shawnguo@...nel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Fabio Estevam <festevam@...il.com>
Subject: Re: PHY issue with SJA1105Q/DP84849I Design
> > If you are truly using MII, then you should remove the RGMII delay
> > properties, and since you are using a 6.1 kernel - hence after kernel
> > commit 5d645df99ac6 ("net: dsa: sja1105: determine PHY/MAC role from PHY
> > interface type") - you should be using phy-mode = "rev-mii" to put this
> > port in MII PHY ("RevMII") mode - to interoperate with the FEC in MII
> > MAC mode.
>
> Okay, I will remove RGMII delay. is phy-mode = "rev-mii" applicable to
> all ports or only for fec port4?
phy-mode indicates what the PHY should be doing. In this case, the
switch is taking the place of the PHY and so the switch MAC needs to
be revMII so that it acts like a PHY. For the other ports of the
switch, you have a real PHY connected, so you want MII.
Andrew
Powered by blists - more mailing lists