From: Andrew Lunn <andrew@lunn.ch>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Vladimir Oltean <olteanv@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"Andrew F. Davis" <afd@ti.com>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org,
Michael Nazzareno Trimarchi <michael@amarulasolutions.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: PHY issue with SJA1105Q/DP84849I Design
Date: Fri, 29 Dec 2023 22:43:48 +0100 [thread overview]
Message-ID: <dc66ab0e-1c63-4a57-98a5-a440d97d13f7@lunn.ch> (raw)
In-Reply-To: <CAMty3ZAOM5+EMw9sLVOq-=CH_sP=1TLAGEMF9LYOZ4aFbNUtsg@mail.gmail.com>
> > 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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-29 21:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 7:19 PHY issue with SJA1105Q/DP84849I Design Jagan Teki
2023-12-22 14:51 ` Vladimir Oltean
2023-12-26 7:41 ` Jagan Teki
2023-12-26 15:30 ` Vladimir Oltean
2023-12-26 16:49 ` Andrew Lunn
2023-12-26 17:00 ` Andrew Lunn
2023-12-26 17:05 ` Vladimir Oltean
2023-12-29 11:42 ` Jagan Teki
2023-12-29 15:25 ` Vladimir Oltean
2023-12-29 20:18 ` Jagan Teki
2023-12-29 21:43 ` Andrew Lunn [this message]
2023-12-30 11:28 ` Vladimir Oltean
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=dc66ab0e-1c63-4a57-98a5-a440d97d13f7@lunn.ch \
--to=andrew@lunn.ch \
--cc=afd@ti.com \
--cc=f.fainelli@gmail.com \
--cc=festevam@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=jagan@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@amarulasolutions.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=shawnguo@kernel.org \
/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