mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v8 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema
Date: Fri, 18 Sep 2026 09:03:01 +0200	[thread overview]
Message-ID: <20260918070301.GA21010@marmottus.net> (raw)
In-Reply-To: <178967572953.22033.7825853149442957564@kernel.org>

On Thu, Sep 17, 2026 at 08:08:49PM +0000, netdev-bot+sashiko@kernel.org wrote:
>[Severity: Low]
>The description says the 14 MHz limit applies only to w5100 while 80 MHz
>applies to w5200/w5500, but the single maximum: 80000000 is applied to all
>three compatibles.  Should the w5100 limit be expressed as a conditional so
>dt_binding_check can enforce it?
>

The user should know which SPI speed to use here. I don't think
leaving the scheme open to higher speeds is a real issue.

>[Severity: Low]
>This changes the recommended trigger type from IRQ_TYPE_EDGE_FALLING in the
>removed .txt binding to IRQ_TYPE_LEVEL_LOW, and the deleted text also
>claimed "w5x00 natively generates falling edge interrupts".  Could the
>commit message mention this correction?
>
>The new value agrees with the driver, which requests the device interrupt
>level-low in w5100_probe():
>
>    err = request_threaded_irq(priv->irq, NULL, w5100_interrupt,
>                               IRQF_TRIGGER_LOW | IRQF_ONESHOT,
>                               netdev_name(ndev), ndev);
>
>The commit message body only says the binding is converted from plain text
>to DT schema.  The only record of the trigger change is the v8 changelog
>line "Change edge-falling to level-low" below the --- separator, which git
>does not keep.
>

Nitpicky but I can add a line in the commit body.

Arthur

  reply	other threads:[~2026-09-18  7:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  8:06 [PATCH net-next v8 0/3] w5100: restore GPIO-based link detection Arthur Crepin Leblond
2026-09-15  8:06 ` [PATCH net-next v8 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema Arthur Crepin Leblond
2026-09-17 20:08   ` netdev-bot+sashiko
2026-09-18  7:03     ` Arthur Crepin Leblond [this message]
2026-09-15  8:06 ` [PATCH net-next v8 2/3] dt-bindings: net: wiznet,w5100: add link status interrupt Arthur Crepin Leblond
2026-09-17 10:04   ` Krzysztof Kozlowski
2026-09-17 12:02     ` Arthur Crepin Leblond
2026-09-17 20:08   ` netdev-bot+sashiko
2026-09-18  7:17     ` Arthur Crepin Leblond
2026-09-15  8:06 ` [PATCH net-next v8 3/3] w5100: detect carrier state using link status bit and optional interrupt Arthur Crepin Leblond
2026-09-17 20:08   ` netdev-bot+sashiko
2026-09-18 12:18     ` 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=20260918070301.GA21010@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®