[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201210141610.GG2638572@lunn.ch>
Date: Thu, 10 Dec 2020 15:16:10 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Steen Hegelund <steen.hegelund@...rochip.com>
Cc: Kishon Vijay Abraham I <kishon@...com>,
Vinod Koul <vkoul@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Lars Povlsen <lars.povlsen@...rochip.com>,
Bjarni Jonasson <bjarni.jonasson@...rochip.com>,
Microchip UNG Driver List <UNGLinuxDriver@...rochip.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v9 3/4] phy: Add Sparx5 ethernet serdes PHY driver
> > So why are returning link up information?
>
> Yes that was a bit of a hijacking of the function. I will remove that.
> I also removed the dependency on this behaviour in the client driver in the
> meantime.
>
> I think a status function on the generic phy would be useful, but I will
> take that as separate issue.
In this context of an Ethernet SERDES, do you actually need it? You
would normally look at the PCS link status to determine if the link is
up. But it is useful debug information. If the PCS is down, but the
PHY indicates up, you can guess you have a protocol misconfiguration.
What exactly does link at this level mean? And thinking of the wider
uses of the PHY subsystem, what would link mean at this level for
SATA, PCIe, USB? Don't these all have some protocol level above
similar to Ethernet PCS which is the real determiner of link?
Andrew
Powered by blists - more mailing lists