[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<GV2PR04MB1174071C79AC14657B83E289696D7A@GV2PR04MB11740.eurprd04.prod.outlook.com>
Date: Wed, 19 Nov 2025 15:20:00 +0000
From: Claudiu Manoil <claudiu.manoil@....com>
To: Wei Fang <wei.fang@....com>, Vladimir Oltean <vladimir.oltean@....com>,
Clark Wang <xiaoning.wang@....com>, "andrew+netdev@...n.ch"
<andrew+netdev@...n.ch>, "davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>, "kuba@...nel.org"
<kuba@...nel.org>, "pabeni@...hat.com" <pabeni@...hat.com>
CC: Aziz Sellami <aziz.sellami@....com>, "imx@...ts.linux.dev"
<imx@...ts.linux.dev>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3 net-next 2/3] net: enetc: set external PHY address in
IERB for i.MX94 ENETC
> -----Original Message-----
> From: Wei Fang <wei.fang@....com>
> Sent: Wednesday, November 19, 2025 12:26 PM
[...]
> Subject: [PATCH v3 net-next 2/3] net: enetc: set external PHY address in IERB
> for i.MX94 ENETC
>
> NETC IP has only one external master MDIO interface (eMDIO) for managing
> the external PHYs. ENETC can use the interfaces provided by the EMDIO
> function or its port MDIO to access and manage its external PHY. Both
> the EMDIO function and the port MDIO are all virtual ports of the eMDIO.
>
> The difference is that the EMDIO function is a 'global port', it can
> access all the PHYs on the eMDIO, but port MDIO can only access its own
> PHY. To ensure that ENETC can only access its own PHY through port MDIO,
> LaBCR[MDIO_PHYAD_PRTAD] needs to be set, which represents the address
> of
> the external PHY connected to ENETC. If the accessed PHY address is not
> consistent with LaBCR[MDIO_PHYAD_PRTAD], then the MDIO access initiated
> by port MDIO will be invalid.
>
> Signed-off-by: Wei Fang <wei.fang@....com>
> ---
Reviewed-by: Claudiu Manoil <claudiu.manoil@....com>
Powered by blists - more mailing lists