Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp4918037rwl; Mon, 3 Apr 2023 11:27:18 -0700 (PDT) X-Google-Smtp-Source: AKy350YEDLr/vdNVXVKjpucaz9hfADOtmdWK0uwI9rlu4tU5QvE9ptRDn7bKspj1HFBvAdwhWknl X-Received: by 2002:a17:907:a4b:b0:93e:9362:7602 with SMTP id be11-20020a1709070a4b00b0093e93627602mr42655021ejc.50.1680546438043; Mon, 03 Apr 2023 11:27:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680546438; cv=none; d=google.com; s=arc-20160816; b=Xl3RNEEY9DYEJT5g80rymaZ3FXACXJyWj0yHe9MYs9a2JLNVDAMv/2aGIruc9tcpR8 Gh0AGihJpLTthUwaKMEgAwfe8aqa2rdzYK2JHN5//5K5GZvDENUDBMS9lL+NsCGFkvqe i19YTwSwazB7qB9CEu8jmlOiYLPxd3KE4Y2iH6//kjnfg1BNhuevTFXIDeFSwdaXyRDn P4auKGgHmK3iJCTT3aYZe5OKaCckBdwHJmkked0vYxsEWcrK0YgKx57hICf1F048WvLy 0OR6muZRhYTAuB09Hj5E9bGKKLfFZQrhVlj89Layi5kK79aGcRSvmrKf9RGE07VOyL4R Ymlg== 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-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=vTPQ+7gkVO2Aps53RpVv5KHzFQYEl7mi0a1sEGJvNMg=; b=Vxr/2cgIetNZYBPU7dWpJzo6mEORJYvZ4Y113tOhHNAWOYzydFuZG9cv7CJ1sKtVNH /nm1rqpTdCfIm/I5f82XqhExreOsRmwnl7QaZbHhnTnxdyrBGAnSh5B+DpfS5gGZzABw xZ95GOGnA0XbOVBgD3MWFN6pRtbyLczv6A8eCBYb9dTkHqp5gUnDmHaC+K64rFoRJH0r RC/Gd/+EZth5sBLOwglHCEM6viCNqhp5/UqT+VGAxGScdOBX7JFlAENyyRFJkTpokdEb 58kX1WOvX3cEKpm0GUEZUn0gJFgMgk/bA5AVpx34ltWSkNkbpIa2VyxNh91cpU/Q14bo S9Gg== ARC-Authentication-Results: i=1; mx.google.com; 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 g9-20020a170906394900b0093fcc6295f7si730731eje.773.2023.04.03.11.26.53; Mon, 03 Apr 2023 11:27:18 -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; 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 S232279AbjDCSOB (ORCPT + 99 others); Mon, 3 Apr 2023 14:14:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40736 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232433AbjDCSN4 (ORCPT ); Mon, 3 Apr 2023 14:13:56 -0400 Received: from fudo.makrotopia.org (fudo.makrotopia.org [IPv6:2a07:2ec0:3002::71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E28961BC1; Mon, 3 Apr 2023 11:13:54 -0700 (PDT) Received: from local by fudo.makrotopia.org with esmtpsa (TLS1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.96) (envelope-from ) id 1pjOgd-0001gS-2R; Mon, 03 Apr 2023 20:13:47 +0200 Date: Mon, 3 Apr 2023 19:13:43 +0100 From: Daniel Golle To: =?utf-8?B?QXLEsW7DpyDDnE5BTA==?= Cc: devicetree@vger.kernel.org, netdev@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Rob Herring , Krzysztof Kozlowski , Andrew Lunn , Florian Fainelli , Vladimir Oltean , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Matthias Brugger , AngeloGioacchino Del Regno , Sean Wang , Landen Chao , DENG Qingfang , Philipp Zabel , Russell King , Sam Shih , Lorenzo Bianconi , John Crispin , Felix Fietkau Subject: Re: [PATCH net-next v2 00/14] net: dsa: add support for MT7988 Message-ID: References: <53d89480-936d-25b1-6422-cda7769de369@arinc9.com> <73ce771f-3a13-b1c7-659d-7e1c236fdd0b@arinc9.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <73ce771f-3a13-b1c7-659d-7e1c236fdd0b@arinc9.com> X-Spam-Status: No, score=0.0 required=5.0 tests=SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 Mon, Apr 03, 2023 at 08:50:11PM +0300, Arınç ÜNAL wrote: > On 3.04.2023 20:42, Daniel Golle wrote: > > Hi Arınç, > > > > On Mon, Apr 03, 2023 at 08:08:19PM +0300, Arınç ÜNAL wrote: > > > On 3.04.2023 04:16, Daniel Golle wrote: > > > > The MediaTek MT7988 SoC comes with a built-in switch very similar to > > > > previous MT7530 and MT7531. However, the switch address space is mapped > > > > into the SoCs memory space rather than being connected via MDIO. > > > > Using MMIO simplifies register access and also removes the need for a bus > > > > lock, and for that reason also makes interrupt handling more light-weight. > > > > > > > > Note that this is different from previous SoCs like MT7621 and MT7623N > > > > which also came with an integrated MT7530-like switch which yet had to be > > > > accessed via MDIO. > > > > > > > > Split-off the part of the driver registering an MDIO driver, then add > > > > another module acting as MMIO/platform driver. > > > > > > > > The whole series has been tested on various MediaTek boards: > > > > * MT7623A + MT7530 (BPi-R2) > > > > * MT7986A + MT7531 (BPi-R3) > > > > * MT7988A reference board > > > > > > You did not address the incorrect information I pointed out here. Now that > > > > I'm sorry, that was certainly not intentional and I may have missed > > your comments. Actually it doesn't look like they have made it to the > > netdev list archive or patchwork either. > > > > > the patch series is applied, people reading this on the merge branch commit > > > will be misled by the misinformation. > > > > I've changed Kconfig stuff according to your recommendation and also > > addressed possible misleading USXGMII and 10GBase-KR support by > > introducing MT7988-specific functions and using 'internal' PHY mode. > > So which of your comments have not been addressed? > > https://lore.kernel.org/netdev/c11c86e4-5f8e-5b9b-1db5-e3861b2bade6@arinc9.com/ Strange that both emails didn't make it into patchwork. > > > > > > > > > > > > > > Changes since v1: > > > > * use 'internal' PHY mode where appropriate > > > > * use regmap_update_bits in mt7530_rmw > > > > * improve dt-bindings > > > > > > As a maintainer of the said dt-bindings, I pointed out almost 7 things for > > > you to change. Of those 7 points, you only did one, a trivial grammar > > > change. The patch series is applied now so one of us maintainers (you are > > > one too now) need to fix it with additional patches. > > > > I was also surprised the series made it to net-next so quickly, but it > > wasn't me applying it, I merly posted v2 with all comments I received > > addressed. > > > > Me and supposedly also netdevbpf maintainers use patchwork to track > > patches and whether comments have been addressed. Can you point me to > > emails with the comments which haven't been addressed there? Looking in > > patchwork for the dt-bindings patch [1] I don't see any comments there. > > https://lore.kernel.org/netdev/a7ab2828-dc03-4847-c947-c7685841f884@arinc9.com/ > > > > > > > Thank you for reviewing! > > > > > > Daniel > > > > > > [1]: See patchwork tracking for RFCv3, v1 and v2. Prior to RFCv3 the series > > didn't have the dt-bindings addition, I introduced it with RFCv3 when splitting > > the series into many small changes: > > https://patchwork.kernel.org/project/netdevbpf/patch/9b504e3e88807bfb62022c0877451933d30abeb5.1680105013.git.daniel@makrotopia.org/ > > https://patchwork.kernel.org/project/netdevbpf/patch/fef2cb2fe3d2b70fa46e93107a0c862f53bb3bfa.1680180959.git.daniel@makrotopia.org/ > > https://patchwork.kernel.org/project/netdevbpf/patch/dffacdb59aea462c9f7d4242cf9563a04cf79807.1680483896.git.daniel@makrotopia.org/ > > Although I've been a maintainer for the dt-bindings schema for quite some > time, I was somehow missed as a recipient on RFC v3. Yeah, that was my mistake. get_maintainers.pl comes up with unreadable unicode garbage, probably something is wrong in my local Perl setup. So I always manually replace your name with readable UTF-8, but I missed that for RFC v3.