From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Prabhakar <prabhakar.csengg@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Jose Abreu <joabreu@synopsys.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 2/3] dt-bindings: net: Document GBETH bindings for Renesas RZ/V2H(P) SoC
Date: Sun, 2 Mar 2025 19:28:09 +0000 [thread overview]
Message-ID: <Z8SxSU9lOgbNf0he@shell.armlinux.org.uk> (raw)
In-Reply-To: <a1dbb3e8-4a52-4cc2-8e7b-cf240f726d5e@lunn.ch>
On Sun, Mar 02, 2025 at 08:10:26PM +0100, Andrew Lunn wrote:
> > + interrupts:
> > + items:
> > + - description: Subsystem interrupt
> > + - description: The interrupt to manage the remote wake-up packet detection
> > + - description: The interrupt that occurs when Tx/Rx enters/exits the LPI state
> > + - description: Per-channel transmission-0 completion interrupt
> > + - description: Per-channel transmission-1 completion interrupt
> > + - description: Per-channel transmission-2 completion interrupt
> > + - description: Per-channel transmission-3 completion interrupt
> > + - description: Per-channel receive-0 completion interrupt
> > + - description: Per-channel receive-1 completion interrupt
> > + - description: Per-channel receive-2 completion interrupt
> > + - description: Per-channel receive-3 completion interrupt
> > +
> > + interrupt-names:
> > + items:
> > + - const: macirq
> > + - const: eth_wake_irq
> > + - const: eth_lpi
> > + - const: tx0
> > + - const: tx1
> > + - const: tx2
> > + - const: tx3
> > + - const: rx0
> > + - const: rx1
> > + - const: rx2
> > + - const: rx3
>
> There has already been a discussion about trying to make the clock
> names more uniform. But what about interrupts? Which of these are in
> the IP databook? What names does the databook use for these
> interrupts?
From a quick look, I haven't found anything that suggests the above
is possible, but it clearly is... so I'll look more tomorrow.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-03-02 19:28 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 18:18 [PATCH 0/3] Add GBETH glue layer driver for Renesas RZ/V2H(P) SoC Prabhakar
2025-03-02 18:18 ` [PATCH 1/3] dt-bindings: net: dwmac: Increase 'maxItems' for 'interrupts' and 'interrupt-names' Prabhakar
2025-03-03 15:26 ` Rob Herring
2025-03-03 15:58 ` Lad, Prabhakar
2025-03-03 16:34 ` Andrew Lunn
2025-03-03 20:40 ` Lad, Prabhakar
2025-03-02 18:18 ` [PATCH 2/3] dt-bindings: net: Document GBETH bindings for Renesas RZ/V2H(P) SoC Prabhakar
2025-03-02 19:10 ` Andrew Lunn
2025-03-02 19:28 ` Russell King (Oracle) [this message]
2025-03-02 21:33 ` Andrew Lunn
2025-03-03 15:15 ` Rob Herring
2025-03-02 19:25 ` Andrew Lunn
2025-03-02 20:41 ` Lad, Prabhakar
2025-03-02 21:01 ` Russell King (Oracle)
2025-03-02 21:22 ` Lad, Prabhakar
2025-03-02 21:39 ` Andrew Lunn
2025-03-02 21:43 ` Lad, Prabhakar
2025-03-02 21:49 ` Russell King (Oracle)
2025-03-02 21:51 ` Russell King (Oracle)
2025-03-02 22:03 ` Lad, Prabhakar
2025-03-02 18:18 ` [PATCH 3/3] net: stmmac: Add DWMAC glue layer for Renesas GBETH Prabhakar
2025-03-02 19:33 ` Russell King (Oracle)
2025-03-02 20:05 ` Russell King (Oracle)
2025-03-02 21:20 ` Lad, Prabhakar
2025-03-02 21:44 ` Russell King (Oracle)
2025-03-02 22:02 ` Lad, Prabhakar
2025-03-03 11:19 ` Russell King (Oracle)
2025-03-03 16:04 ` Lad, Prabhakar
2025-03-03 16:32 ` Russell King (Oracle)
2025-03-05 21:26 ` Lad, Prabhakar
2025-03-06 0:31 ` Russell King (Oracle)
2025-03-08 13:20 ` Lad, Prabhakar
2025-03-04 6:58 ` Biju Das
2025-03-04 10:00 ` Russell King (Oracle)
2025-03-04 10:56 ` Biju Das
2025-03-04 11:16 ` Russell King (Oracle)
2025-03-04 14:04 ` Geert Uytterhoeven
2025-03-03 9:41 ` Lad, Prabhakar
2025-03-03 9:58 ` Russell King (Oracle)
2025-03-03 10:58 ` Russell King (Oracle)
2025-03-03 10:40 ` Geert Uytterhoeven
2025-03-03 10:44 ` Lad, Prabhakar
2025-03-03 10:54 ` Russell King (Oracle)
2025-03-06 13:11 ` Geert Uytterhoeven
2025-03-08 12:44 ` Lad, Prabhakar
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=Z8SxSU9lOgbNf0he@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=joabreu@synopsys.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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;
as well as URLs for NNTP newsgroup(s).