From: Arthur Crepin Leblond <arthur@marmottus.net>
To: netdev-bot+sashiko@kernel.org
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, arnd@arndb.de,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v10 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema
Date: Thu, 24 Sep 2026 09:12:00 +0200 [thread overview]
Message-ID: <20260924071200.GA19102@marmottus.net> (raw)
In-Reply-To: <179021495314.2160803.14503162237139110651@kernel.org>
On Thu, Sep 24, 2026 at 01:55:53AM +0000, netdev-bot+sashiko@kernel.org wrote:
>[Severity: Low]
>The description here says the w5100 tops out around 14 MHz, but the only
>machine-checkable constraint is the loosest value, 80000000, and it applies
>to all three compatibles.
>
>Should the w5100 limit be expressed as a conditional instead, so that it is
>actually validated?
>
> allOf:
> - if:
> properties:
> compatible:
> contains:
> const: wiznet,w5100
> then:
> properties:
> spi-max-frequency:
> maximum: 14000000
>
>As written, a node with:
>
> compatible = "wiznet,w5100";
> spi-max-frequency = <80000000>;
>
>passes dt_binding_check and dtbs_check with no diagnostic. Nothing in
>drivers/net/ethernet/wiznet/ looks at spi->max_speed_hz either, so the
>14 MHz figure is not enforced anywhere.
>
>This is still the case at the end of the series: the allOf if/then block
>added later by "dt-bindings: net: wiznet,w5100: add link status interrupt"
>only constrains interrupts, and spi-max-frequency keeps the unconditional
>80 MHz ceiling.
>
>Separately, the old wiznet,w5x00.txt documented the 80 MHz figure for the
>w5500 only:
>
> - spi-max-frequency: Maximum frequency of the SPI bus when accessing
> the w5500.
>
>The new schema extends that ceiling to w5100 and w5200 as well. Could the
>commit message mention that change?
I don't think it is really an issue here, the user must put a relevant
max spi frequency when creating their DT.
>
>[ ... ]
>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index df8ab9b824024..9f84e4c8163e4 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -29450,6 +29450,12 @@ M: Miloslav Trmac <mitr@volny.cz>
>> S: Maintained
>> F: drivers/input/misc/wistron_btns.c
>>
>> +WIZNET W5100 ETHERNET DRIVER
>> +M: Arthur Crepin Leblond <arthur@marmottus.net>
>> +L: netdev@vger.kernel.org
>> +S: Maintained
>> +F: Documentation/devicetree/bindings/net/wiznet,w5100.yaml
>> +
>
>[Severity: Low]
>The commit message describes only the .txt to .yaml conversion and the
>trigger type change, but this hunk also creates a new maintainership entry.
>The "v8: Add a myself in MAINTAINERS" note is below the --- line and will
>not land in git history.
>
>Could the commit message describe the MAINTAINERS addition too?
>
>Also, at this commit the section is titled "WIZNET W5100 ETHERNET DRIVER"
>while the only F: pattern matches the YAML binding, so get_maintainer.pl
>still reports no maintainer for drivers/net/ethernet/wiznet/. That gap is
>closed later in the series: "w5100: detect carrier state using link status
>bit and optional interrupt" adds F: drivers/net/ethernet/wiznet/ to the
>same block. Would it make sense to add that F: line here, where the section
>is introduced?
>
>--
Will be fixed in v11
Arthur
next prev parent reply other threads:[~2026-09-24 7:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 10:52 [PATCH net-next v10 0/3] w5100: restore GPIO-based link detection Arthur Crepin Leblond
2026-09-21 10:52 ` [PATCH net-next v10 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema Arthur Crepin Leblond
2026-09-24 1:55 ` netdev-bot+sashiko
2026-09-24 7:12 ` Arthur Crepin Leblond [this message]
2026-09-21 10:52 ` [PATCH net-next v10 2/3] dt-bindings: net: wiznet,w5100: add link status interrupt Arthur Crepin Leblond
2026-09-24 1:55 ` netdev-bot+sashiko
2026-09-24 7:14 ` Arthur Crepin Leblond
2026-09-21 10:52 ` [PATCH net-next v10 3/3] w5100: detect carrier state using link status bit and optional interrupt Arthur Crepin Leblond
2026-09-21 15:31 ` Arthur Crepin Leblond
2026-09-24 1:55 ` netdev-bot+sashiko
2026-09-24 8:26 ` 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=20260924071200.GA19102@marmottus.net \
--to=arthur@marmottus.net \
--cc=andrew+netdev@lunn.ch \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®