[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <97a56e9d-6a8e-46b4-9e66-5544b470a270@lunn.ch>
Date: Tue, 15 Jul 2025 17:16:05 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Maxime Chevallier <maxime.chevallier@...tlin.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, thomas.petazzoni@...tlin.com,
Jakub Kicinski <kuba@...nel.org>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Russell King <linux@...linux.org.uk>,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Vladimir Oltean <vladimir.oltean@....com>,
Köry Maincent <kory.maincent@...tlin.com>,
Oleksij Rempel <o.rempel@...gutronix.de>,
Simon Horman <horms@...nel.org>, Shuah Khan <shuah@...nel.org>,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH net-next v3 1/3] net: netdevsim: Add PHY support in
netdevsim
> So should we instead move to a netdevsim PHY model where we would
> emulate an mdio bus and use a pure genphy driver instead ?
I think what you have is a good start. It actually requires somebody
who is interesting in testing to take it further. And i doubt a pure
genphy driver is sufficient, i guess it will need a driver specific
for simulation. There is some things you can test via the PHY driver
API, and other stuff you need to emulate registers. So it will end up
with a hybrid of both.
Andrew
Powered by blists - more mailing lists