[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eae7d246-49c3-486e-bc62-cdb49d6b1d72@lunn.ch>
Date: Sat, 10 Aug 2024 19:26:16 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Tristram.Ha@...rochip.com
Cc: Woojung Huh <woojung.huh@...rochip.com>, UNGLinuxDriver@...rochip.com,
devicetree@...r.kernel.org, Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Marek Vasut <marex@...x.de>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 1/4] dt-bindings: net: dsa: microchip: add SGMII
port support to KSZ9477 switch
On Fri, Aug 09, 2024 at 04:38:37PM -0700, Tristram.Ha@...rochip.com wrote:
> From: Tristram Ha <tristram.ha@...rochip.com>
>
> The SGMII module of KSZ9477 switch can be setup in 3 ways: 0 for direct
> connect, 1 for 1000BaseT SFP, and 2 for 10/100/1000 SFP.
>
> SFP is typically used so the default is 1. The driver can detect
> 10/100/1000 SFP and change the mode to 2. For direct connect this mode
> has to be explicitly set to 0 as driver cannot detect that
> configuration.
Could you explain this in more detail. Other SGMII blocks don't need
this. Why is this block special?
Has this anything to do with in-band signalling?
Andrew
Powered by blists - more mailing lists