[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YuSrpbUrcZh5QotE@lunn.ch>
Date: Sat, 30 Jul 2022 05:55:17 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Maxime Chevallier <maxime.chevallier@...tlin.com>
Cc: davem@...emloft.net, Rob Herring <robh+dt@...nel.org>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, thomas.petazzoni@...tlin.com,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
linux-arm-kernel@...ts.infradead.org,
Richard Cochran <richardcochran@...il.com>,
Horatiu.Vultur@...rochip.com, Allan.Nielsen@...rochip.com,
UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH net-next v3 1/4] net: phy: Introduce QUSGMII PHY mode
On Fri, Jul 29, 2022 at 05:33:53PM +0200, Maxime Chevallier wrote:
> The QUSGMII mode is a derivative of Cisco's USXGMII standard. This
> standard is pretty similar to SGMII, but allows for faster speeds, and
> has the build-in bits for Quad and Octa variants (like QSGMII).
>
> The main difference with SGMII/QSGMII is that USXGMII/QUSGMII re-uses
> the preamble to carry various information, named 'Extensions'.
>
> As of today, the USXGMII standard only mentions the "PCH" extension,
> which is used to convey timestamps, allowing in-band signaling of PTP
> timestamps without having to modify the frame itself.
>
> This commit adds support for that mode. When no extension is in use, it
> behaves exactly like QSGMII, although it's not compatible with QSGMII.
>
> Signed-off-by: Maxime Chevallier <maxime.chevallier@...tlin.com>
Reviewed-by: Andrew Lunn <andrew@...n.ch>
Andrew
Powered by blists - more mailing lists