Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 126DEC636D3 for ; Fri, 10 Feb 2023 12:35:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231898AbjBJMfR (ORCPT ); Fri, 10 Feb 2023 07:35:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53638 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231405AbjBJMfP (ORCPT ); Fri, 10 Feb 2023 07:35:15 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6F01834F64; Fri, 10 Feb 2023 04:35:14 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 04A4161DB1; Fri, 10 Feb 2023 12:35:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 485F0C433EF; Fri, 10 Feb 2023 12:35:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1676032513; bh=VE48/BFpY9oqV03SRPNJIzQxVKnk2kNg22dC8+ipOPk=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=m3crUoVr31IK6DkF6r2xv+oUJ9j9szbJiXsY85GnpZZSagUplipp4rCZvRZAqDfD9 q0DJONooGPfKWdUqeXuRc58ZZE0p4ipgOurvU2N9R7Jau5JUVKSYsCgu6qlUtyUCVY yseO1lXnIczQz9Nzv/bDYrfwf49NARJ6OJHTbVLV7hBLVjgRWNrdBGuRmKQj4MndYa JW5QBP4mC0tBrFH3Kn7ggKwkDumY4J0RJ4PP7vtAFbcuFukekdMGqS1LyeE9gbcxZz td0Ik1rZXQMDl/UljsItTQnHd7NnxqTn88nk3L5bjJJQKJNXHvt2mfROMJ9aXOOim7 peEq8UEVhjfkA== Message-ID: Date: Fri, 10 Feb 2023 13:35:02 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [PATCH v2 03/11] dt-bindings: arm: mediatek: add 'mediatek,pn_swap' property Content-Language: en-US To: "Russell King (Oracle)" Cc: Daniel Golle , netdev@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Heiner Kallweit , Lorenzo Bianconi , Mark Lee , John Crispin , Felix Fietkau , AngeloGioacchino Del Regno , Matthias Brugger , DENG Qingfang , Landen Chao , Sean Wang , Paolo Abeni , Jakub Kicinski , Eric Dumazet , "David S. Miller" , Vladimir Oltean , Florian Fainelli , Andrew Lunn , Jianhui Zhao , =?UTF-8?Q?Bj=c3=b8rn_Mork?= References: <514ec4b8-ef78-35c1-2215-22884fca87d4@kernel.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/02/2023 13:23, Russell King (Oracle) wrote: > On Fri, Feb 10, 2023 at 10:34:17AM +0000, Russell King (Oracle) wrote: >> On Thu, Feb 09, 2023 at 12:30:27PM +0100, Krzysztof Kozlowski wrote: >>> On 08/02/2023 23:30, Daniel Golle wrote: >>>> Hm, none of the current PCS (or PHY) drivers are represented by a >>>> syscon node... (and maybe that's the mistake in first place?) >>> >>> Yes. >> >> Nos, it isn't. > > To expand on this - I have no idea why you consider it a mistake that > apparently all PCS aren't represented by a syscon node. > > PCS is a sub-block in an ethernet system, just the same as a MAC is a > sub-block. PCS can appear in several locations of an ethernet system, > but are generally found either side of a serial ethernet link such > as 1000base-X, SGMII, USXGMII, 10Gbase-R etc. > > So, one can find PCS within an ethernet PHY - and there may be one > facing the MAC connection, and there will be another facing the media. > We generally do not need to separate these PCS from the PHY itself > because we view the PHY as one whole device. > > The optional PCS on the MAC side of the link is something that we > need to know about, because this has to be configured to talk to the > PHY, or to configure and obtain negotiation results from in the case of > fibre links. > > PCS on the MAC side are not a system level device, they are very much a > specific piece of ethernet hardware in the same way that the MAC is, > and we don't represent the MAC as a syscon node. There is no reason > to do so with PCS. > > These PCS on the MAC side tend to be accessed via direct MMIO accesses, > or over a MDIO bus. > > There's other blocks in the IEEE 802.3 ethernet layering, such as the > PMA/PMD module (which for the MAC side we tend to model with the > drivers/phy layer) - but again, these also appear in ethernet PHYs > in order to produce the electrical signals for e.g. twisted pair > ethernet. > > So, to effectively state that you consider that PCS should always be > represented as a syscon node is rather naieve, and really as a DT > reviewer you should not be making such decisions, but soliciting > opinions from those who know this subject area in detail _whether_ > they are some kind of system controller before making such a > decision. Daniel switched to private emails, so unfortunately our talk is not visible here, nevertheless thanks for the feedback. Much appreciated! Best regards, Krzysztof