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>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH 2/2] dt-bindings: net: Document support for Aeonsemi PHYs
Date: Mon, 24 Mar 2025 12:09:36 -0500 [thread overview]
Message-ID: <20250324170936.GA584083-robh@kernel.org> (raw)
In-Reply-To: <20250323225439.32400-2-ansuelsmth@gmail.com>
On Sun, Mar 23, 2025 at 11:54:27PM +0100, Christian Marangi wrote:
> Document support for Aeonsemi PHYs and the requirement of a firmware to
> correctly work. Also document the max number of LEDs supported and what
> PHY ID expose when no firmware is loaded.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
> .../bindings/net/aeonsemi,as21xxx.yaml | 87 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 88 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/aeonsemi,as21xxx.yaml
>
> diff --git a/Documentation/devicetree/bindings/net/aeonsemi,as21xxx.yaml b/Documentation/devicetree/bindings/net/aeonsemi,as21xxx.yaml
> new file mode 100644
> index 000000000000..0549abcd3929
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/aeonsemi,as21xxx.yaml
> @@ -0,0 +1,87 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/aeonsemi,as21xxx.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Aeonsemi AS21XXX Ethernet PHY
> +
> +maintainers:
> + - Christian Marangi <ansuelsmth@gmail.com>
> +
> +description: |
> + Aeonsemi AS21xxx Ethernet PHYs requires a firmware to be loaded to actually
> + work. The same firmware is compatible with various PHYs of the same family.
> +
> + A PHY with not firmware loaded will be exposed on the MDIO bus with ID
> + 0x7500 0x7500
> +
> + This can be done and is implemented by OEM in 2 different way:
> + - Attached SPI flash directly to the PHY with the firmware. The PHY
> + will self load the firmware in the presence of this configuration.
> + - Manually provided firmware loaded from a file in the filesystem.
> +
> + Each PHY can support up to 5 LEDs.
> +
> +allOf:
> + - $ref: ethernet-phy.yaml#
> +
> +select:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - ethernet-phy-id7500.7500
> + required:
> + - compatible
> +
> +properties:
> + reg:
> + maxItems: 1
> +
> + firmware-name:
> + description: specify the name of PHY firmware to load
maxItems: 1
as I think we allow more than 1.
Not required? Then what is the default name (default: ???)?
> +
> +required:
> + - compatible
> + - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/leds/common.h>
> +
> + mdio {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ethernet-phy@1f {
> + compatible = "ethernet-phy-id7500.7500",
> + "ethernet-phy-ieee802.3-c45";
> +
> + reg = <31>;
> + firmware-name = "as21x1x_fw.bin";
> +
> + leds {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + led@0 {
> + reg = <0>;
> + color = <LED_COLOR_ID_GREEN>;
> + function = LED_FUNCTION_LAN;
> + function-enumerator = <0>;
> + default-state = "keep";
> + };
> +
> + led@1 {
> + reg = <1>;
> + color = <LED_COLOR_ID_GREEN>;
> + function = LED_FUNCTION_LAN;
> + function-enumerator = <1>;
> + default-state = "keep";
> + };
> + };
> + };
> + };
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9a2df6d221bd..59a863dd3b70 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -649,6 +649,7 @@ AEONSEMI PHY DRIVER
> M: Christian Marangi <ansuelsmth@gmail.com>
> L: netdev@vger.kernel.org
> S: Maintained
> +F: Documentation/devicetree/bindings/net/aeonsemi,as21xxx.yaml
> F: drivers/net/phy/as21xxx.c
>
> AF8133J THREE-AXIS MAGNETOMETER DRIVER
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-03-24 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 22:54 [net-next PATCH 1/2] net: phy: Add support for new Aeonsemi PHYs Christian Marangi
2025-03-23 22:54 ` [net-next PATCH 2/2] dt-bindings: net: Document support for " Christian Marangi
2025-03-24 17:09 ` Rob Herring [this message]
2025-03-24 3:19 ` [net-next PATCH 1/2] net: phy: Add support for new " kernel test robot
2025-03-24 14:03 ` Andrew Lunn
2025-03-24 14:16 ` Christian Marangi
2025-03-24 15:16 ` Andrew Lunn
2025-03-25 12:04 ` Christian Marangi
2025-03-25 20:33 ` Andrew Lunn
2025-03-25 20:41 ` Christian Marangi
2025-03-25 21:36 ` Russell King (Oracle)
2025-03-24 14:55 ` Russell King (Oracle)
2025-03-29 18:51 ` kernel test robot
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=20250324170936.GA584083-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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.