[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a2f67eb6-63eb-40fb-a181-b320481514f1@lunn.ch>
Date: Thu, 1 Aug 2024 22:16:00 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Jijie Shao <shaojijie@...wei.com>
Cc: yisen.zhuang@...wei.com, salil.mehta@...wei.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
horms@...nel.org, shenjian15@...wei.com, wangpeiyang1@...wei.com,
liuyonglong@...wei.com, sudongming1@...wei.com,
xujunsheng@...wei.com, shiyongbang@...wei.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH net-next 08/10] net: hibmcge: Implement workqueue and
some ethtool_ops functions
> If the network port is linked, but the link fails between the SGMII and PHY,
> is there any method to find out the cause?
>
> I've had a problem with phy link but SGMII no link due to poor contact.
So a hardware design issue? Has it been solved now, or is there
shipped hardware with this problem?
I would say there is a difference between the first prototype board,
and real products. If the real product has issues, then we should try
to address it. If it is just a prototype board, i would ignore it.
One option might be to expose your PCS as a phylib PCS. Do you get
interrupts from it when it has link up? Link down? phylink will then
combine media side status with PCS status.
Andrew
Powered by blists - more mailing lists