Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Arthur Crepin Leblond" <arthur@marmottus.net>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH net-next v5 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema
Date: Fri, 14 Aug 2026 08:58:45 +0000	[thread overview]
Message-ID: <20260814085846.0B61D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260813-wiznet-link-gpio-v5-1-ac8046f24413@marmottus.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The YAML device tree example will fail compilation during `make dt_binding_check` due to unresolved phandles (`<&eth1_pins>` and `<&gpio>`).
--

--- Patch [1]: [PATCH net-next v5 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema ---
commit fcc3d575c269eac63488595e1b5b27fd36f552f7
Author: Arthur Crepin Leblond <arthur@marmottus.net>

dt-bindings: net: wiznet,w5100: convert to DT schema

Convert the Wiznet w5x00 SPI Ethernet controller binding from
plain text to DT schema.

> diff --git a/Documentation/devicetree/bindings/net/wiznet,w5100.yaml b/Documentation/devicetree/bindings/net/wiznet,w5100.yaml
> new file mode 100644
> index 0000000000000..217f301db182b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/wiznet,w5100.yaml

[ ... ]

> +examples:
> +  - |
> +    /* Example (for Raspberry Pi with pin control stuff for GPIO irq) */
> +
> +    #include <dt-bindings/interrupt-controller/irq.h>
> +
> +    spi {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        ethernet@0 {
> +            compatible = "wiznet,w5500";
> +            reg = <0>;
> +            pinctrl-names = "default";
> +            pinctrl-0 = <&eth1_pins>;
> +            interrupt-parent = <&gpio>;

[Severity: Low]
Will this example fail compilation during make dt_binding_check due to
unresolved phandles? It looks like &eth1_pins and &gpio are referenced
here, but their node definitions were not carried over from the original
text binding.

> +            interrupts = <25 IRQ_TYPE_EDGE_FALLING>;
> +            spi-max-frequency = <30000000>;
> +            local-mac-address = [ a0 b0 c0 d0 e0 f0 ];
> +        };
> +    };
> +...

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260813-wiznet-link-gpio-v5-0-ac8046f24413@marmottus.net?part=1

  parent reply	other threads:[~2026-08-14  8:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13  8:58 [PATCH net-next v5 0/3] w5100: restore GPIO-based link detection Arthur Crepin Leblond
2026-08-13  8:58 ` [PATCH net-next v5 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema Arthur Crepin Leblond
2026-08-14  7:15   ` Krzysztof Kozlowski
2026-08-14 10:32     ` Arthur Crepin Leblond
2026-08-14  8:58   ` sashiko-bot [this message]
2026-08-13  8:58 ` [PATCH net-next v5 2/3] dt-bindings: net: wiznet,w5100: add link status interrupt Arthur Crepin Leblond
2026-08-14  7:17   ` Krzysztof Kozlowski
2026-08-14  8:58   ` sashiko-bot
2026-08-13  8:58 ` [PATCH net-next v5 3/3] w5100: detect carrier state using link status bit and optional interrupt Arthur Crepin Leblond
2026-08-14  8:58   ` sashiko-bot
2026-08-14 11:02   ` Arthur Crepin Leblond

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=20260814085846.0B61D1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=arthur@marmottus.net \
    --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