netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: shawnguo@kernel.org, s.hauer@pengutronix.de,
	Russell King <rmk+kernel@armlinux.org.uk>,
	arm-soc <arm@kernel.org>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/3] ARM: dts: imx51: ZII: Add missing phy-mode
Date: Fri, 7 Apr 2023 19:50:34 +0300	[thread overview]
Message-ID: <20230407165034.qvmx7algembpsona@skbuf> (raw)
In-Reply-To: <b5e96d31-6290-44e5-b829-737e40f0ef35@lunn.ch>

On Fri, Apr 07, 2023 at 06:10:31PM +0200, Andrew Lunn wrote:
> On Fri, Apr 07, 2023 at 06:41:59PM +0300, Vladimir Oltean wrote:
> > On Fri, Apr 07, 2023 at 05:25:01PM +0200, Andrew Lunn wrote:
> > > The DSA framework has got more picky about always having a phy-mode
> > > for the CPU port. The imx51 Ethernet supports MII, and RMII. Set the
> > > switch phy-mode based on how the SoC Ethernet port has been
> > > configured.
> > > 
> > > Additionally, the cpu label has never actually been used in the
> > > binding, so remove it.
> > > 
> > > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> > > ---
> > 
> > In theory, an MII MAC-to-MAC connection should have phy-mode = "mii" on
> > one end and phy-mode = "rev-mii" on the other, right?
> 
> In theory, yes. As far as i understand, it makes a difference to where
> the clock comes from. rev-mii is a clock provider i think.
> 
> But from what i understand of the code, and the silicon, this property
> is going to be ignored, whatever value you give it. phy-mode is only
> used and respected when the port can support 1000Base-X, SGMII, and
> above, or use its built in PHY. For MII, GMII, RMII, RGMII the port
> setting is determined by strapping resistors.

If it's ignored, even better, one more reason to make it rev-mii and
not mii, no compatibility concerns with the driver not understanding the
difference...

> The DSA core however does care that there is a phy-mode, even if it is
> ignored. I hope after these patches land we can turn that check into
> enforce mode, and that then unlocks Russell to make phylink
> improvement.
> 
> 	Andrew
>

  reply	other threads:[~2023-04-07 16:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 15:25 [PATCH 0/3] Add missing DSA properties for marvell switches Andrew Lunn
2023-04-07 15:25 ` [PATCH 1/3] ARM: dts: imx51: ZII: Add missing phy-mode Andrew Lunn
2023-04-07 15:41   ` Vladimir Oltean
2023-04-07 16:10     ` Andrew Lunn
2023-04-07 16:50       ` Vladimir Oltean [this message]
2023-04-07 17:06         ` Andrew Lunn
2023-04-10 10:00       ` Vladimir Oltean
2023-04-10 10:37         ` Russell King (Oracle)
2023-04-10 15:24           ` Vladimir Oltean
2023-04-10 11:59         ` Andrew Lunn
2023-04-10 12:35         ` Andrew Lunn
2023-04-10 13:11           ` Vladimir Oltean
2023-04-10 14:56             ` Andrew Lunn
2023-04-07 15:25 ` [PATCH 2/3] ARM: dts: imx6qdl: Add missing phy-mode and fixed links Andrew Lunn
2023-04-07 15:25 ` [PATCH 3/3] ARM64: dts: freescale: ZII: Add missing phy-mode Andrew Lunn

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=20230407165034.qvmx7algembpsona@skbuf \
    --to=vladimir.oltean@nxp.com \
    --cc=andrew@lunn.ch \
    --cc=arm@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=s.hauer@pengutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).