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,
krzysztof.kozlowski@oss.qualcomm.com
Subject: Re: [PATCH net-next v7 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema
Date: Fri, 11 Sep 2026 17:30:13 +0200 [thread overview]
Message-ID: <20260911153013.GA9585@marmottus.net> (raw)
In-Reply-To: <178895753846.219967.8860843467900146377@kernel.org>
On Wed, Sep 09, 2026 at 12:38:58PM +0000, netdev-bot+sashiko@kernel.org wrote:
>Would it make sense to either describe/constrain the type as level-low in
>the schema, or have the driver pass IRQF_TRIGGER_NONE and honour the DT
>type?
I'll change the falling edge to low.
>Would an allOf/if:properties:compatible:contains: block per part be
>better here, or a description explaining why 80 MHz is safe for all
>three?
I would maybe rephrase the description then but a allOf sounds
overkill, w5500 and w5200 seem to support theoretically up to 80 MHz
but going that high will probably cause some signal distortion. I
would consider this a user mistake to use an unstable frequency.
Arthur
next prev parent reply other threads:[~2026-09-11 15:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 12:35 [PATCH net-next v7 0/3] w5100: restore GPIO-based link detection Arthur Crepin Leblond
2026-09-04 12:35 ` [PATCH net-next v7 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema Arthur Crepin Leblond
2026-09-05 12:36 ` sashiko-bot
2026-09-09 12:38 ` netdev-bot+sashiko
2026-09-11 15:30 ` Arthur Crepin Leblond [this message]
2026-09-04 12:35 ` [PATCH net-next v7 2/3] dt-bindings: net: wiznet,w5100: add link status interrupt Arthur Crepin Leblond
2026-09-09 12:39 ` netdev-bot+sashiko
2026-09-11 15:33 ` Arthur Crepin Leblond
2026-09-11 15:56 ` Arthur Crepin Leblond
2026-09-04 12:36 ` [PATCH net-next v7 3/3] w5100: detect carrier state using link status bit and optional interrupt Arthur Crepin Leblond
2026-09-05 12:36 ` sashiko-bot
2026-09-11 15:40 ` Arthur Crepin Leblond
2026-09-09 12:39 ` netdev-bot+sashiko
2026-09-10 11:27 ` Paolo Abeni
2026-09-10 12:28 ` 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=20260911153013.GA9585@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=krzysztof.kozlowski@oss.qualcomm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.