From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pidgin.makrotopia.org (pidgin.makrotopia.org [185.142.180.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 17F39E3; Tue, 12 Dec 2023 08:43:14 -0800 (PST) Received: from local by pidgin.makrotopia.org with esmtpsa (TLS1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.96.2) (envelope-from ) id 1rD5qP-0006en-2c; Tue, 12 Dec 2023 16:42:55 +0000 Date: Tue, 12 Dec 2023 16:42:45 +0000 From: Daniel Golle To: Conor Dooley Cc: "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Chunfeng Yun , Vinod Koul , Kishon Vijay Abraham I , Felix Fietkau , John Crispin , Sean Wang , Mark Lee , Lorenzo Bianconi , Matthias Brugger , AngeloGioacchino Del Regno , Andrew Lunn , Heiner Kallweit , Russell King , Alexander Couzens , Qingfang Deng , SkyLake Huang , Philipp Zabel , netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, linux-phy@lists.infradead.org Subject: Re: [RFC PATCH net-next v3 1/8] dt-bindings: phy: mediatek,xfi-pextp: add new bindings Message-ID: References: <20231212-renderer-strobe-2b46652cd6e7@spud> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20231212-renderer-strobe-2b46652cd6e7@spud> On Tue, Dec 12, 2023 at 04:21:38PM +0000, Conor Dooley wrote: > On Tue, Dec 12, 2023 at 03:46:26AM +0000, Daniel Golle wrote: >=20 > > + mediatek,usxgmii-performance-errata: > > + $ref: /schemas/types.yaml#/definitions/flag > > + description: > > + USXGMII0 on MT7988 suffers from a performance problem in 10GBase= -R > > + mode which needs a work-around in the driver. The work-around is > > + enabled using this flag. >=20 > Why do you need a property for this if you know that it is present on > the MT7988? Because it is only present in one of the two SerDes channels. Channel 0 needs the work-around, Channel 1 doesn't. See also this commit in the vendor driver for reference[1]. We previously discussed that[2] and it was decided that a property would be the prefered way to represent this as there aren't any other per-instance differences which would justify another compatible. [1]: https://git01.mediatek.com/plugins/gitiles/openwrt/feeds/mtk-openwrt-f= eeds/+/a500d94cd47e279015ce22947e1ce396a7516598%5E%21/#F0 [2]: https://patchwork.kernel.org/comment/25592845/