Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Oskari Lemmela" <oskari@lemmela.net>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH net-next v2 1/2] dt-bindings: net: realtek,rtl82xx: document RTL8224 packages
Date: Tue, 06 Oct 2026 20:23:47 +0000	[thread overview]
Message-ID: <sashiko-outbox-162426@kernel.org> (raw)
In-Reply-To: <20261005201540.913977-2-oskari@lemmela.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: net: generic compatible in example fails schema validation
--

commit 6e9280e0153fb3196c44f745f9db18bcf7971400
Author: Oskari Lemmela <oskari@lemmela.net>

dt-bindings: net: realtek,rtl82xx: document RTL8224 packages

This commit updates the realtek,rtl82xx bindings to document RTL8224 PHY
packages and adds an example demonstrating multiple child PHY nodes within an
ethernet-phy-package.

> diff --git a/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml b/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml
> index 07b39ef1fc624..ca52c3ae19f7a 100644
> --- a/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml
> +++ b/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml
[ ... ]
> @@ -90,9 +100,45 @@ examples:
>          #address-cells = <1>;
>          #size-cells = <0>;
>  
[ ... ]
> +        ethernet-phy-package@1 {
> +            reg = <1>;
> +            #address-cells = <1>;
> +            #size-cells = <0>;
> +
> +            ethernet-phy@1 {
> +                compatible = "ethernet-phy-ieee802.3-c45";

[Severity: Low]
Does this generic compatible string cause a schema validation warning during
make dt_binding_check? 

Because this generic string is not listed in the schema's compatible enum,
the implicit select logic generated for this schema fails to match the
example node. The dt-schema tool strictly requires examples to match their
enclosing schema, so this mismatch will trigger a validation error.

> +                reg = <1>;
> +                enet-phy-pair-order = <0>;
> +            };
> +
> +            ethernet-phy@2 {
> +                compatible = "ethernet-phy-ieee802.3-c45";
> +                reg = <2>;
> +                enet-phy-pair-order = <0>;
> +            };
[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261005201540.913977-1-oskari@lemmela.net?part=1

  reply	other threads:[~2026-10-06 20:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 20:15 [PATCH net-next v2 0/2] Support unaligned RTL8224 PHY packages Oskari Lemmela
2026-10-05 20:15 ` [PATCH net-next v2 1/2] dt-bindings: net: realtek,rtl82xx: document RTL8224 packages Oskari Lemmela
2026-10-06 20:23   ` sashiko-bot [this message]
2026-10-08  8:18   ` netdev-bot+sashiko
2026-10-05 20:15 ` [PATCH net-next v2 2/2] net: phy: realtek: support unaligned RTL8224 PHY packages Oskari Lemmela
2026-10-08  8:18   ` netdev-bot+sashiko
2026-10-08 17:12     ` Oskari Lemmelä
2026-10-08 18:02       ` Andrew Lunn

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=sashiko-outbox-162426@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=oskari@lemmela.net \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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