Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Selvamani Rajagopal" <Selvamani.Rajagopal@onsemi.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH net-next v3 13/14] dt-bindings: net: add onsemi's S2500
Date: Sat, 30 May 2026 18:41:59 +0000	[thread overview]
Message-ID: <20260530184200.676F61F00898@smtp.kernel.org> (raw)
In-Reply-To: <CY8PR02MB92494D02A1209BC9BC72EAC883162@CY8PR02MB9249.namprd02.prod.outlook.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing `spi-max-frequency` in the device tree binding properties, required list, and example for an SPI peripheral.
--

commit ad5dbf88af08e186c5df6e55d01443c7fc4840ab
Author: Selvamani Rajagopal <Selvamani.Rajagopal@onsemi.com>

dt-bindings: net: add onsemi's S2500

Add YAML device tree binding for the onsemi S2500 IEEE 802.3cg
compliant Ethernet transceiver device.

> diff --git a/Documentation/devicetree/bindings/net/onnn,s2500.yaml b/Documentation/devicetree/bindings/net/onnn,s2500.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/onnn,s2500.yaml
[ ... ]
> +properties:
> +  compatible:
> +    const: onnn,s2500
> +
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    description:
> +      Interrupt from MAC-PHY asserted in the event of Receive Chunks
> +      Available, Transmit Chunk Credits Available and Extended Status
> +      Event.
> +    maxItems: 1

[Severity: Medium]
Since this is an SPI peripheral, should spi-max-frequency be defined in the
properties section with device-specific maximum frequency constraints?

> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts

[Severity: Medium]
Would it be appropriate to add spi-max-frequency to this required list?
Omitting it allows incomplete device tree nodes to pass schema validation,
even though the SPI host controller needs it to configure the bus clock
speed.

> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/interrupt-controller/irq.h>
> +    spi {
> +      #address-cells = <1>;
> +      #size-cells = <0>;
> +
> +      ethernet@0 {
> +        compatible = "onnn,s2500";
> +        reg = <0>;
> +        pinctrl-names = "default";
> +        pinctrl-0 = <&eth0_pins>;
> +        interrupt-parent = <&gpio>;
> +        interrupts = <25 IRQ_TYPE_LEVEL_LOW>;

[Severity: Medium]
Is spi-max-frequency missing from this example? If developers copy this node
configuration, could it fail to configure the SPI host properly at runtime
without the max frequency property?

> +      };
> +    };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/CY8PR02MB92494D02A1209BC9BC72EAC883162@CY8PR02MB9249.namprd02.prod.outlook.com?part=13

      parent reply	other threads:[~2026-05-30 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 18:41 [PATCH net-next v3 13/14] dt-bindings: net: add onsemi's S2500 Selvamani Rajagopal
2026-05-30  9:00 ` Krzysztof Kozlowski
2026-05-30 14:48   ` Andrew Lunn
2026-05-30 16:15     ` Selvamani Rajagopal
2026-05-30 18:41 ` sashiko-bot [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=20260530184200.676F61F00898@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Selvamani.Rajagopal@onsemi.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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