netdev - Re: [PATCH net-next 0/3] net: enetc: add port MDIO support for both i.MX94 and i.MX95

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <fef3dbdc-50e4-4388-a32e-b5ae9aaaed6d@lunn.ch>
Date: Fri, 31 Oct 2025 13:31:20 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Wei Fang <wei.fang@....com>
Cc: Claudiu Manoil <claudiu.manoil@....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>,
	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 net-next 0/3] net: enetc: add port MDIO support for both
 i.MX94 and i.MX95

> What we get from the DT is the external PHY address, just like the mdio
> driver, this external PHY address based on the board, ENETC needs to
> know its external PHY address so that its port MIDO can work properly.

So i don't get this. MDIO is just a bus, two lines. It can have up to
32 devices on it. The bus master should not need to have any idea what
devices are on it, it just twiddles the lines as requested.

Why does it need to know the external PHY address? In general, the
only thing which needs to know the PHY address is phylib.

	Andrew