[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YLqLzOltcb6jan+B@lunn.ch>
Date: Fri, 4 Jun 2021 22:23:40 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Madalin Bucur <madalin.bucur@....com>
Cc: Russell King <linux@...linux.org.uk>,
Pali Rohár <pali@...nel.org>,
Igal Liberman <Igal.Liberman@...escale.com>,
Shruti Kanetkar <Shruti@...escale.com>,
Emil Medve <Emilian.Medve@...escale.com>,
Scott Wood <oss@...error.net>,
Rob Herring <robh+dt@...nel.org>,
Michael Ellerman <mpe@...erman.id.au>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Camelia Alexandra Groza (OSS)" <camelia.groza@....nxp.com>
Subject: Re: Unsupported phy-connection-type sgmii-2500 in
arch/powerpc/boot/dts/fsl/t1023rdb.dts
> The "sgmii-2500" compatible in that device tree describes an SGMII HW
> block, overclocked at 2.5G. Without that overclocking, it's a plain
> Cisco (like) SGMII HW block. That's the reason you need to disable it's
> AN setting when overclocked. With the proper Reset Configuration Word,
> you could remove the overclocking and transform that into a plain "sgmii".
> Thus, the dts compatible describes the HW, as it is.
It sounds like the hardware is capable of swapping between SGMII and
2500BaseX.
What we have in DT in this case is not describing the hardware, but
how we configure the hardware. It is one of the few places we abuse DT
for configuration.
Andrew
Powered by blists - more mailing lists