Received: by 2002:ac0:e350:0:0:0:0:0 with SMTP id g16csp670382imn; Fri, 29 Jul 2022 20:58:22 -0700 (PDT) X-Google-Smtp-Source: AGRyM1uTHboxYOBbWY2EHmK+3+pQx1VwIbAFyQwhoa6t4qw0Po0sAWMfdbCxJiwYuYzJ39QXhmOj X-Received: by 2002:a05:6402:15a:b0:431:71b9:86f3 with SMTP id s26-20020a056402015a00b0043171b986f3mr6242397edu.249.1659153502471; Fri, 29 Jul 2022 20:58:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659153502; cv=none; d=google.com; s=arc-20160816; b=OWgGAoByL2MRATMuCbs1ZWYoWfa9MY2ivxQt1mxI278rBzsFU8bshvkH/PpgJ+gJVY cf1ja2gOx95idV54ycmvIfSY6JKAjtH70uz7/KyzW3197AbsHgIb/oedaagldI9s6N9u bD1bjqVlFJaiG34b9Rx272l5+7dDZJSJzfsyH8lkR+mTGkuEWlcty2L7BVv8va5UsXah arjaUUTdPadXWSWbVKnwgctp2jWoXKPMvd125osJg34xGKH+tuWYMzqw0AtCnsE+WT9c yyRoiPnKsgtnE9KYFsYDmEOl0fV5KeE537wk0zPyE7Q9Es8YLXrL3ciflZN/XQK+JI9a G03w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=gjwGvuIYlf7YURpygwYL3YCCMDNSe/5O6oVE1XLk23k=; b=u++FkrmsE9yuzIkrig3maakQiJN9Vw+A/YMFrh8IgFaEmZozVvZLmmAaY8Yl5fxD++ x7u3L73nFPZpBiR4rwAO1Ye25MTDEGtnhRlVcIzc1gxkXVYN6blchZCe/TjF3JnwYhYi FG7d8t8bf/jDau02IO05fZktxwMSQlypy7YpkMEHokjWmgCFpkbXRALOKuyKYQWBxnAr o4IR1jhdIwDGR8zh4GSxT3aOYPy8nB3gmBwswTIXGs8Z53ERLV2V6W5gkYqOTv6lLRIr W61PTR3vG6Uh4quq6Lwein8AE+u4r2WJYR0UX5g6SlD0kBc62zJn1dt+3YStpitoHAzF MgMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=ZYUfs1+1; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z6-20020a17090665c600b007101a8a5b89si4042285ejn.943.2022.07.29.20.57.57; Fri, 29 Jul 2022 20:58:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=ZYUfs1+1; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239839AbiG3DzZ (ORCPT + 99 others); Fri, 29 Jul 2022 23:55:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47434 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230251AbiG3DzX (ORCPT ); Fri, 29 Jul 2022 23:55:23 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [185.16.172.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BF78814D2E; Fri, 29 Jul 2022 20:55:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=gjwGvuIYlf7YURpygwYL3YCCMDNSe/5O6oVE1XLk23k=; b=ZYUfs1+1e4ls90l1z7FI1IjfsV y6HXSTTXO7KiFdvT1ncL/nrAV0qzX9copWCDrD4jsLPOBJ0DXiSmDKjs2GmgTEiDOKhAxFHVYTPW4 u7RAi7MtzrxbdSacHnD7VIKCqzLMo2j5I/3An1YCyxid+o0Oo7feza5JE8fVY3ffckOc=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1oHdZN-00BzR1-Tv; Sat, 30 Jul 2022 05:55:17 +0200 Date: Sat, 30 Jul 2022 05:55:17 +0200 From: Andrew Lunn To: Maxime Chevallier Cc: davem@davemloft.net, Rob Herring , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, thomas.petazzoni@bootlin.com, Florian Fainelli , Heiner Kallweit , Russell King , linux-arm-kernel@lists.infradead.org, Richard Cochran , Horatiu.Vultur@microchip.com, Allan.Nielsen@microchip.com, UNGLinuxDriver@microchip.com Subject: Re: [PATCH net-next v3 1/4] net: phy: Introduce QUSGMII PHY mode Message-ID: References: <20220729153356.581444-1-maxime.chevallier@bootlin.com> <20220729153356.581444-2-maxime.chevallier@bootlin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220729153356.581444-2-maxime.chevallier@bootlin.com> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 Reviewed-by: Andrew Lunn Andrew