From mboxrd@z Thu Jan 1 00:00:00 1970 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8F079C5AE5B for ; Mon, 20 Nov 2023 17:42:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=9F8VK1/BCC6WB9KIHJwEwYfm0/OK0ayQQUqBv9x+1a0=; b=LtwvYzHGBQy8eg mDr2nfT2XM6hFJI3u6kPhUbEeG7e+ZPFw1XtXKQA2sKMmAolb12t+kdmF0o4bsoj50BJlNdz5fkml hjur2agS1vIgwmx7OwYCetOVcH/NZWp1/jaQUVukHzJJdeC8mjI3ZGuu1BTFwBSeYtWk0Kz2P3BXT 6hz04tIhQhqp9l1TAaICuNZBrAlhpojNlnZA7ej4bu3N9qdW+RDFq+59RrhjPnRuN4qDeuix20hJl J+NNGMtco5rZa0tuVW3YKLRfBAPqBYRWlUBMxPEGLu/j1BeFeKt59n88vjdaskZPvIFAmiFuDFc6V 1rfpglz+7Wg9ViudAXGg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1r58HF-00Dx1J-1c; Mon, 20 Nov 2023 17:41:41 +0000 Received: from mail-il1-f177.google.com ([209.85.166.177]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1r58HC-00Dwxi-2O; Mon, 20 Nov 2023 17:41:40 +0000 Received: by mail-il1-f177.google.com with SMTP id e9e14a558f8ab-35b059b07dfso3244185ab.0; Mon, 20 Nov 2023 09:41:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700502096; x=1701106896; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=ZLZXIZ9nL5/cSx66YwTtOh2+aHxea+g3SVnUlPh+FEo=; b=J/aX4rHXa35NdgRm4pqSN61ZWNYPzIAh1nr+t/UtAEaXqSfIXhwC2q0S5V7C5Jj8d/ l1ZFKdPkh56OHSRsQVp/DI6e1q09d2UyZ1jWRBZwVMLqF03L34Ydakc4Gxc0pmbw3/Bs CQIItyfZJVeijsvEZAB65jrljVNaHlHG8gXdJZS91eJP0nLGne++A+shMKaNKZRGXpGp KsZR8gdu68GrXnRXyLtQKccTsplYN7UrSRo7hN53c0LyeAeMLnhLKJdJzv2kQSlE3OLs RaF5amMpLiXZoONluEDUWFU67eNrz3V8QDED9FR1mzLsEyWw6EokHrYQmOU3c5jOdafK 2RTg== X-Gm-Message-State: AOJu0YxY1WuvTVlqARhj1rGQPfQJX3s7nFB2jaI5R1f81aV4wzLbu+8y OpPcT6d1FGhtpsiIbs9lNw== X-Google-Smtp-Source: AGHT+IE7LLdCgHclxhBtKeaxESMvFFwRvbO4prdXF+F7uXEM4kZFAFBlPgYkjWcTW5fnFTdDF4lhlQ== X-Received: by 2002:a05:6e02:1c49:b0:359:4fde:6297 with SMTP id d9-20020a056e021c4900b003594fde6297mr10797167ilg.30.1700502096357; Mon, 20 Nov 2023 09:41:36 -0800 (PST) Received: from herring.priv ([64.188.179.252]) by smtp.gmail.com with ESMTPSA id m23-20020a0566380ad700b00451b5feb80fsm2075627jab.8.2023.11.20.09.41.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 20 Nov 2023 09:41:35 -0800 (PST) Received: (nullmailer pid 2455759 invoked by uid 1000); Mon, 20 Nov 2023 17:41:33 -0000 Date: Mon, 20 Nov 2023 10:41:33 -0700 From: Rob Herring To: Christian Marangi Cc: "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Krzysztof Kozlowski , Conor Dooley , Andy Gross , Bjorn Andersson , Konrad Dybcio , Andrew Lunn , Heiner Kallweit , Russell King , Florian Fainelli , Broadcom internal kernel review list , Daniel Golle , Qingfang Deng , SkyLake Huang , Matthias Brugger , AngeloGioacchino Del Regno , David Epping , Vladimir Oltean , "Russell King (Oracle)" , Harini Katakam , Simon Horman , Robert Marko , netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org Subject: Re: [net-next RFC PATCH 03/14] dt-bindings: net: document ethernet PHY package nodes Message-ID: <20231120174133.GB2378814-robh@kernel.org> References: <20231120135041.15259-1-ansuelsmth@gmail.com> <20231120135041.15259-4-ansuelsmth@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20231120135041.15259-4-ansuelsmth@gmail.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231120_094138_783460_DB0DE711 X-CRM114-Status: GOOD ( 24.34 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Nov 20, 2023 at 02:50:30PM +0100, Christian Marangi wrote: > Document ethernet PHY package nodes used to describe PHY shipped in > bundle of 4-5 PHY. These particular PHY require specific PHY in the > package for global onfiguration of the PHY package. > > Example are PHY package that have some regs only in one PHY of the > package and will affect every other PHY in the package, for example > related to PHY interface mode calibration or global PHY mode selection. > > The PHY package node should use the global-phys property and the > global-phy-names to define PHY in the package required by the PHY driver > for global configuration. > > It's also possible to specify the property phy-mode to specify that the > PHY package sets a global PHY interface mode and every PHY of the > package requires to have the same PHY interface mode. > > Signed-off-by: Christian Marangi > --- > .../bindings/net/ethernet-phy-package.yaml | 86 +++++++++++++++++++ > 1 file changed, 86 insertions(+) > create mode 100644 Documentation/devicetree/bindings/net/ethernet-phy-package.yaml > > diff --git a/Documentation/devicetree/bindings/net/ethernet-phy-package.yaml b/Documentation/devicetree/bindings/net/ethernet-phy-package.yaml > new file mode 100644 > index 000000000000..2aa109e155d9 > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/ethernet-phy-package.yaml > @@ -0,0 +1,86 @@ > +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/net/ethernet-phy-package.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Ethernet PHY Package Common Properties > + > +maintainers: > + - Christian Marangi ' > + > +properties: > + $nodename: > + pattern: "^ethernet-phy-package(-[0-9]+)?$" > + > + compatible: > + const: ethernet-phy-package > + > + '#address-cells': > + description: number of address cells for the MDIO bus > + const: 1 > + > + '#size-cells': > + description: number of size cells on the MDIO bus > + const: 0 > + > + global-phys: > + $ref: /schemas/types.yaml#/definitions/phandle-array > + minItems: 1 > + maxItems: 31 > + description: > + List of phandle to the PHY in the package required and > + used to configure the PHY package. > + > + global-phy-names: > + $ref: /schemas/types.yaml#/definitions/string-array > + minItems: 1 > + maxItems: 31 > + description: > + List of names of the PHY defined in global-phys. > + > + phy-connection-type: > + $ref: /schemas/net/ethernet-phy-mode-types.yaml#definitions/phy-connection-type > + description: > + Specifies global interface type for the PHY package. > + > + phy-mode: > + $ref: "#/properties/phy-connection-type" > + > +patternProperties: > + ^ethernet-phy(@[a-f0-9]+)?$: > + $ref: /schemas/net/ethernet-phy.yaml# > + > +required: > + - compatible > + > +dependencies: > + global-phy-names: [global-phys] > + > +unevaluatedProperties: false > + > +examples: > + - | > + ethernet { You mean 'mdio' here, right? > + #address-cells = <1>; > + #size-cells = <0>; > + > + ethernet-phy-package { This doesn't work. Child nodes of MDIO bus must be an MDIO device with an address. What you need is a node with all the addresses of the device: mdio { ... ethernet-phy@1 { compatible = "vendor,specifc-compatible-for-device"; reg = <1>, <4>; ... }; }; There's also some MDIO devices which define a secondary address as a child device. Maybe those are similar to your situation. I don't recall which ones offhand. > + compatible = "ethernet-phy-package"; > + #address-cells = <1>; > + #size-cells = <0>; > + > + global-phys = <&phy4>; > + global-phy-names = "base"; > + > + ethernet-phy@1 { > + compatible = "ethernet-phy-ieee802.3-c22"; > + reg = <1>; > + }; > + > + phy4: ethernet-phy@4 { > + compatible = "ethernet-phy-ieee802.3-c22"; > + reg = <4>; > + }; > + }; > + }; > -- > 2.40.1 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel