From: Andrew Lunn <andrew@lunn.ch>
To: Hanyuan Zhao <hanyuan-z@qq.com>
Cc: davem@davemloft.net, kuba@kernel.org, andrew+netdev@lunn.ch,
edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: net: add enc28j60's irq-gpios node description and binding example
Date: Sun, 9 Mar 2025 16:46:48 +0100 [thread overview]
Message-ID: <a406f363-0f2d-4ebb-8eec-053d9d148502@lunn.ch> (raw)
In-Reply-To: <tencent_8031D017AFE5E266C43F62C916C709009E06@qq.com>
On Sun, Mar 09, 2025 at 03:48:38PM +0800, Hanyuan Zhao wrote:
> This patch allows the kernel to automatically requests the pin, configures
> it as an input, and converts it to an IRQ number, according to a GPIO
> phandle specified in device tree. This simplifies the process by
> eliminating the need to manually define pinctrl and interrupt nodes.
> Additionally, it is necessary for platforms that do not support pin
> configuration and properties via the device tree.
>
> Signed-off-by: Hanyuan Zhao <hanyuan-z@qq.com>
> ---
> .../bindings/net/microchip,enc28j60.txt | 24 +++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/microchip,enc28j60.txt b/Documentation/devicetree/bindings/net/microchip,enc28j60.txt
> index a8275921a896..e6423635e55b 100644
> --- a/Documentation/devicetree/bindings/net/microchip,enc28j60.txt
> +++ b/Documentation/devicetree/bindings/net/microchip,enc28j60.txt
The DT Maintainers have a strong preference that you first convert to
yaml, and then make extension.
> @@ -8,6 +8,8 @@ the SPI master node.
> Required properties:
> - compatible: Should be "microchip,enc28j60"
> - reg: Specify the SPI chip select the ENC28J60 is wired to
> +
> +Required interrupt properties with pin control subsystem:
> - interrupts: Specify the interrupt index within the interrupt controller (referred
> to above in interrupt-parent) and interrupt type. The ENC28J60 natively
> generates falling edge interrupts, however, additional board logic
You should be able to use the interrupts property and just point it
at a GPIO controller that supports interrupts.
We really need a better understanding of:
> Additionally, it is necessary for platforms that do not support pin
> configuration and properties via the device tree.
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2025-03-09 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 7:48 Hanyuan Zhao
2025-03-09 15:46 ` Andrew Lunn [this message]
2025-03-09 17:55 ` Krzysztof Kozlowski
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=a406f363-0f2d-4ebb-8eec-053d9d148502@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hanyuan-z@qq.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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®