[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e338472c-1f26-e49b-9a2d-7942e6ed4288@gmail.com>
Date: Fri, 4 May 2018 10:04:48 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Antoine Tenart <antoine.tenart@...tlin.com>, davem@...emloft.net,
kishon@...com, linux@...linux.org.uk, gregory.clement@...tlin.com,
andrew@...n.ch, jason@...edaemon.net,
sebastian.hesselbarth@...il.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
thomas.petazzoni@...tlin.com, maxime.chevallier@...tlin.com,
miquel.raynal@...tlin.com, nadavh@...vell.com, stefanc@...vell.com,
ymarkman@...vell.com, mw@...ihalf.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH net-next v2 02/13] net: phy: sfp: handle non-wired SFP
connectors
On 05/04/2018 06:56 AM, Antoine Tenart wrote:
> SFP connectors can be solder on a board without having any of their pins
> (LOS, i2c...) wired. In such cases the SFP link state cannot be guessed,
> and the overall link status reporting is left to other layers.
>
> In order to achieve this, a new SFP_DEV status is added, named UNKNOWN.
> This mode is set when it is not possible for the SFP code to get the
> link status and as a result the link status is reported to be always UP
> from the SFP point of view.
Why represent the SFP in Device Tree then? Why not just declare this is
a fixed link which would avoid having to introduce this "unknown" state.
--
Florian
Powered by blists - more mailing lists