[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <60703503-e592-4467-a942-74400583369d@lunn.ch>
Date: Thu, 14 Sep 2023 14:47:44 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: Maxime Chevallier <maxime.chevallier@...tlin.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jakub Kicinski <kuba@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
Vladimir Oltean <vladimir.oltean@....com>,
Oleksij Rempel <linux@...pel-privat.de>,
Nicolò Veronese <nicveronese@...il.com>,
"thomas.petazzoni@...tlin.com" <thomas.petazzoni@...tlin.com>
Subject: Re: [RFC PATCH net-next 0/7] net: phy: introduce phy numbering
> FWIW when thinking about multiple PHY to a single MAC, what comes to my
> mind is the SIS 900 board, and its driver net/ethernet/sis/sis900.c
>
> It has a function sis900_default_phy() that loops over all phys to find
> one with up-link then to put all but that one in ISOLATE mode. Then when
> the link goes down it loops again to find another up-link.
>
> I guess your series would also help in that case, wouldn't it ?
Yes, it would. However, that driver would need its PHY handling
re-written because it is using the old MII code, not phylib.
Andrew
Powered by blists - more mailing lists