[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5a6f372d-31c3-482d-8925-d2a039643256@lunn.ch>
Date: Tue, 10 Sep 2024 14:21:35 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Jijie Shao <shaojijie@...wei.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, shenjian15@...wei.com, wangpeiyang1@...wei.com,
liuyonglong@...wei.com, chenhao418@...wei.com,
sudongming1@...wei.com, xujunsheng@...wei.com,
shiyongbang@...wei.com, libaihan@...wei.com, jdamato@...tly.com,
horms@...nel.org, kalesh-anakkur.purayil@...adcom.com,
jonathan.cameron@...wei.com, shameerali.kolothum.thodi@...wei.com,
salil.mehta@...wei.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH V9 net-next 03/11] net: hibmcge: Add mdio and hardware
configuration supported in this module
On Tue, Sep 10, 2024 at 03:59:34PM +0800, Jijie Shao wrote:
> this driver using phy through genphy device.
As far as i can see, there is nothing here which limits you to
genphy. The hardware could use any PHY driver which phylib has. In
general, we don't recommend genphy, it is just a fallback driver which
might work, but given the complexity of modern PHYs, also might not.
What PHY do you actually have on the board?
Andrew
Powered by blists - more mailing lists