Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kyle Switch" <kyle.switch@motor-comm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v19 1/3] dt-bindings: net: Document Motorcomm YT8824 PHY package
Date: Thu, 17 Sep 2026 11:00:54 +0000	[thread overview]
Message-ID: <20260917110055.190D61F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260916105504.3262767-2-kyle.switch@motor-comm.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] dt-bindings: net: motorcomm,yt8824: missing phy-mode property definition
- [Low] dt-bindings: net: motorcomm,yt8824: unit address vs reg mismatch in example
--

commit 27c278ec90007d3b5c93bdcce12996609edd6cb2
Author: Kyle Switch <kyle.switch@motor-comm.com>

dt-bindings: net: Document Motorcomm YT8824 PHY package

Motorcomm YT8824 Ethernet PHY is a PHY package of 4 PHYs.

> diff --git a/Documentation/devicetree/bindings/net/motorcomm,yt8824.yaml b/Documentation/devicetree/bindings/net/motorcomm,yt8824.yaml
> new file mode 100644
> index 0000000000000..93e9f765404a3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/motorcomm,yt8824.yaml
> @@ -0,0 +1,59 @@
[ ... ]
> +properties:
> +  compatible:
> +    enum:
> +      - motorcomm,yt8824-package
> +
> +required:
> +  - compatible
> +  - phy-mode

[Severity: Low]
Will this fail `make dt_binding_check`?

It looks like phy-mode is mandated as required here, but there is no
accompanying definition for it in the properties block. Because
`unevaluatedProperties: false` is set below, using this undeclared property
in the example will trigger a schema evaluation error.

> +  - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    mdio {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        ethernet-phy-package@0 {
> +            #address-cells = <1>;
> +            #size-cells = <0>;
> +            compatible = "motorcomm,yt8824-package";
> +            reg = <9>;

[Severity: Low]
Is this unit address intentional?

The example's node uses a unit address of @0, but the reg property is set to
9, which conflicts directly and will cause the Device Tree compiler to emit
a `unit_address_vs_reg` warning.

> +
> +            phy-mode = "internal";
> +
> +            ethernet-phy@4 {
> +                reg = <4>;
> +            };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260916105504.3262767-1-kyle.switch@motor-comm.com?part=1

  parent reply	other threads:[~2026-09-17 11:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 10:55 [PATCH net-next v19 0/3] net: phy: Add driver for Motorcomm Quad 2.5GbE phy Kyle Switch
2026-09-16 10:55 ` [PATCH net-next v19 1/3] dt-bindings: net: Document Motorcomm YT8824 PHY package Kyle Switch
2026-09-16 15:22   ` Rob Herring (Arm)
2026-09-17 11:00   ` sashiko-bot [this message]
2026-09-16 10:55 ` [PATCH net-next v19 2/3] net: phy: Add support for Template Control register for PMA Kyle Switch
2026-09-17 11:00   ` sashiko-bot
2026-09-16 10:55 ` [PATCH net-next v19 3/3] net: phy: Add driver for Motorcomm Quad 2.5GbE phy Kyle Switch

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=20260917110055.190D61F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kyle.switch@motor-comm.com \
    --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