From: Rob Herring <robh@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Philipp Zabel <p.zabel@pengutronix.de>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next RFC PATCH 1/2] dt-bindings: net: Document support for Airoha AN7583 MDIO Controller
Date: Thu, 5 Jun 2025 14:52:25 -0500 [thread overview]
Message-ID: <20250605195225.GA3119975-robh@kernel.org> (raw)
In-Reply-To: <20250527213503.12010-1-ansuelsmth@gmail.com>
On Tue, May 27, 2025 at 11:34:42PM +0200, Christian Marangi wrote:
> Airoha AN7583 SoC have 3 different MDIO Controller. One comes from
> the intergated Switch based on MT7530. The other 2 live under the SCU
> register and expose 2 dedicated MDIO controller.
>
> Document the schema that expose the 2 dedicated MDIO controller.
> Each MDIO controller can be independently reset with the SoC reset line.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
> .../bindings/net/airoha,an7583-mdio.yaml | 78 +++++++++++++++++++
> 1 file changed, 78 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/airoha,an7583-mdio.yaml
>
> diff --git a/Documentation/devicetree/bindings/net/airoha,an7583-mdio.yaml b/Documentation/devicetree/bindings/net/airoha,an7583-mdio.yaml
> new file mode 100644
> index 000000000000..2375f1bf85a2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/airoha,an7583-mdio.yaml
> @@ -0,0 +1,78 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/airoha,an7583-mdio.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Airoha AN7583 Dedicated MDIO Controller
> +
> +maintainers:
> + - Christian Marangi <ansuelsmth@gmail.com>
> +
> +description:
> + Airoha AN7583 SoC have 3 different MDIO Controller.
> +
> + One comes from the intergated Switch based on MT7530.
> +
> + The other 2 (that this schema describe) live under the SCU
> + register supporting both C22 and C45 PHYs.
> +
> +properties:
> + compatible:
> + const: airoha,an7583-mdio
> +
No registers? Looks to me like this middle node should go and the SCU
node should have 2 mdio child nodes at 0xc8 and 0xcc.
It looks like you'll need to define the speed mode bit location somehow
as well.
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 0
> +
> +patternProperties:
> + '^mdio(-(bus|external))@[0-1]$':
Just '^mdio@[0-1]$'
If you need to distinguish external or something, use compatible or
something.
> + type: object
> +
> + $ref: mdio.yaml#
> +
> + properties:
> + reg:
> + minimum: 0
> + maximum: 1
> +
> + resets:
> + maxItems: 1
> +
> + required:
> + - reg
> +
> + unevaluatedProperties: false
> +
> +required:
> + - compatible
> + - "#address-cells"
> + - "#size-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + mdio-controller {
> + compatible = "airoha,an7583-mdio";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + mdio-bus@0 {
> + reg = <0>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ethernet-phy@1f {
> + reg = <31>;
> + };
> + };
> +
> + mdio-bus@1 {
> + reg = <1>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + };
> + };
> --
> 2.48.1
>
prev parent reply other threads:[~2025-06-05 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 21:34 [net-next RFC PATCH 1/2] dt-bindings: net: Document support for Airoha AN7583 MDIO Controller Christian Marangi
2025-05-27 21:34 ` [net-next RFC PATCH 2/2] net: mdio: Add MDIO bus controller for Airoha AN7583 Christian Marangi
2025-05-27 22:36 ` Andrew Lunn
2025-05-27 22:39 ` Christian Marangi
2025-05-27 23:18 ` Andrew Lunn
2025-06-05 19:52 ` Rob Herring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250605195225.GA3119975-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).