[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231127221611.GA4023452-robh@kernel.org>
Date: Mon, 27 Nov 2023 16:16:11 -0600
From: Rob Herring <robh@...nel.org>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>, Andy Gross <agross@...nel.org>, Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konrad.dybcio@...aro.org>, Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>, Russell King <linux@...linux.org.uk>, Matthias Brugger <matthias.bgg@...il.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, Robert Marko <robert.marko@...tura.hr>, netdev@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org
Subject: Re: [net-next PATCH RFC v3 1/8] dt-bindings: net: document ethernet
PHY package nodes
On Sun, Nov 26, 2023 at 02:53:39AM +0100, Christian Marangi wrote:
> Document ethernet PHY package nodes used to describe PHY shipped in
> bundle of 4-5 PHY. The special node describe a container of PHY that
> share common properties. This is a generic schema and PHY package
> should create specialized version with the required additional shared
> properties.
>
> 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 MUST declare the base address used by the PHY driver
> for global configuration by calculating the offsets of the global PHY
> based on the base address of the PHY package and declare the
> "ethrnet-phy-package" compatible.
>
> Each reg of the PHY defined in the PHY package node is absolute and will
> reference the real address of the PHY on the bus.
>
> Signed-off-by: Christian Marangi <ansuelsmth@...il.com>
> ---
> .../bindings/net/ethernet-phy-package.yaml | 75 +++++++++++++++++++
> 1 file changed, 75 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..244d4bc29164
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/ethernet-phy-package.yaml
> @@ -0,0 +1,75 @@
> +# 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 <ansuelsmth@...il.com>
> +
> +description:
> + This schema describe PHY package as simple container for
> + a bundle of PHYs that share the same properties and
> + contains the PHYs of the package themself.
> +
> + Each reg of the PHYs defined in the PHY package node is
> + absolute and describe the real address of the PHY on the bus.
> +
> +properties:
> + $nodename:
> + pattern: "^ethernet-phy-package(@[a-f0-9]+)?$"
> +
> + compatible:
> + const: ethernet-phy-package
In case I wasn't clear, but that compatible is a NAK.
> +
> + reg:
> + minimum: 0
> + maximum: 31
Pretty sure the bus binding already provides these constraints.
> + description:
> + The base ID number for the PHY package.
> + Commonly the ID of the first PHY in the PHY package.
> +
> + Some PHY in the PHY package might be not defined but
> + still exist on the device (just not attached to anything).
> + The reg defined in the PHY package node might differ and
> + the related PHY might be not defined.
> +
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
You are implementing a secondary MDIO bus within this node. It needs a
$ref to mdio.yaml instead of defining the bus again implicitly.
> +
> +patternProperties:
> + ^ethernet-phy(@[a-f0-9]+)?$:
> + $ref: ethernet-phy.yaml#
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: true
> +
> +examples:
> + - |
> + mdio {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ethernet-phy-package@16 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "ethernet-phy-package";
> + reg = <0x16>;
> +
> + ethernet-phy@16 {
> + reg = <0x16>;
> + };
> +
> + phy4: ethernet-phy@1a {
> + reg = <0x1a>;
> + };
This example on its own doesn't make sense. It can't be fully validated
because you allow any additional properties. Drop it.
> + };
> + };
> --
> 2.40.1
>
Powered by blists - more mailing lists