From: Jisheng Zhang <jszhang@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next v2 09/10] dt-bindings: net: snps,dwmac: add per channel irq support
Date: Thu, 10 Aug 2023 23:59:06 +0800 [thread overview]
Message-ID: <ZNUJSvJi+9QsWhAf@xhacker> (raw)
In-Reply-To: <20230808-clapper-corncob-0af7afa65752@spud>
On Tue, Aug 08, 2023 at 08:39:58AM +0100, Conor Dooley wrote:
> On Tue, Aug 08, 2023 at 12:41:50AM +0800, Jisheng Zhang wrote:
> > The IP supports per channel interrupt, add support for this usage case.
> >
> > Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> > ---
> > .../devicetree/bindings/net/snps,dwmac.yaml | 33 +++++++++++++++++++
> > 1 file changed, 33 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/net/snps,dwmac.yaml b/Documentation/devicetree/bindings/net/snps,dwmac.yaml
> > index 5d81042f5634..5a63302ad200 100644
> > --- a/Documentation/devicetree/bindings/net/snps,dwmac.yaml
> > +++ b/Documentation/devicetree/bindings/net/snps,dwmac.yaml
> > @@ -109,6 +109,7 @@ properties:
> > - description: The interrupt that occurs when Rx exits the LPI state
> > - description: The interrupt that occurs when Safety Feature Correctible Errors happen
> > - description: The interrupt that occurs when Safety Feature Uncorrectible Errors happen
> > + - description: All of the rx/tx per-channel interrupts
> >
> > interrupt-names:
> > minItems: 1
> > @@ -118,6 +119,38 @@ properties:
> > - const: eth_lpi
> > - const: sfty_ce
> > - const: sfty_ue
> > + - const: rx0
> > + - const: rx1
> > + - const: rx2
> > + - const: rx3
> > + - const: rx4
> > + - const: rx5
> > + - const: rx6
> > + - const: rx7
> > + - const: rx8
> > + - const: rx9
> > + - const: rx10
> > + - const: rx11
> > + - const: rx12
> > + - const: rx13
> > + - const: rx14
> > + - const: rx15
> > + - const: tx0
> > + - const: tx1
> > + - const: tx2
> > + - const: tx3
> > + - const: tx4
> > + - const: tx5
> > + - const: tx6
> > + - const: tx7
> > + - const: tx8
> > + - const: tx9
> > + - const: tx10
> > + - const: tx11
> > + - const: tx12
> > + - const: tx13
> > + - const: tx14
> > + - const: tx15
>
> I don't think Rob's comment about having added 2 interrupts but 32
> interrupt names has been resolved.
I misunderstood Rob's comment. Now I'm not sure whether dt-binding
can support regex or something or not, or let ask for advice in the
following way: how could I write the dt-binding in this case? I didn't
find similar examples so far. I'm not sure listing possible
description and const properties for all channel interrupts is suitable.
> Did you actually test putting this many interrupts into a node?
> AFAICT, any more than 6 will cause complaints.
I tried 12rx and 12tx interrupts in a node, didn't see dtc warning.
so I guess the complaints are from dtb check? I will try to reproduce
them.
>
> Thanks,
> Conor.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next v2 09/10] dt-bindings: net: snps,dwmac: add per channel irq support
Date: Thu, 10 Aug 2023 23:59:06 +0800 [thread overview]
Message-ID: <ZNUJSvJi+9QsWhAf@xhacker> (raw)
In-Reply-To: <20230808-clapper-corncob-0af7afa65752@spud>
On Tue, Aug 08, 2023 at 08:39:58AM +0100, Conor Dooley wrote:
> On Tue, Aug 08, 2023 at 12:41:50AM +0800, Jisheng Zhang wrote:
> > The IP supports per channel interrupt, add support for this usage case.
> >
> > Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> > ---
> > .../devicetree/bindings/net/snps,dwmac.yaml | 33 +++++++++++++++++++
> > 1 file changed, 33 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/net/snps,dwmac.yaml b/Documentation/devicetree/bindings/net/snps,dwmac.yaml
> > index 5d81042f5634..5a63302ad200 100644
> > --- a/Documentation/devicetree/bindings/net/snps,dwmac.yaml
> > +++ b/Documentation/devicetree/bindings/net/snps,dwmac.yaml
> > @@ -109,6 +109,7 @@ properties:
> > - description: The interrupt that occurs when Rx exits the LPI state
> > - description: The interrupt that occurs when Safety Feature Correctible Errors happen
> > - description: The interrupt that occurs when Safety Feature Uncorrectible Errors happen
> > + - description: All of the rx/tx per-channel interrupts
> >
> > interrupt-names:
> > minItems: 1
> > @@ -118,6 +119,38 @@ properties:
> > - const: eth_lpi
> > - const: sfty_ce
> > - const: sfty_ue
> > + - const: rx0
> > + - const: rx1
> > + - const: rx2
> > + - const: rx3
> > + - const: rx4
> > + - const: rx5
> > + - const: rx6
> > + - const: rx7
> > + - const: rx8
> > + - const: rx9
> > + - const: rx10
> > + - const: rx11
> > + - const: rx12
> > + - const: rx13
> > + - const: rx14
> > + - const: rx15
> > + - const: tx0
> > + - const: tx1
> > + - const: tx2
> > + - const: tx3
> > + - const: tx4
> > + - const: tx5
> > + - const: tx6
> > + - const: tx7
> > + - const: tx8
> > + - const: tx9
> > + - const: tx10
> > + - const: tx11
> > + - const: tx12
> > + - const: tx13
> > + - const: tx14
> > + - const: tx15
>
> I don't think Rob's comment about having added 2 interrupts but 32
> interrupt names has been resolved.
I misunderstood Rob's comment. Now I'm not sure whether dt-binding
can support regex or something or not, or let ask for advice in the
following way: how could I write the dt-binding in this case? I didn't
find similar examples so far. I'm not sure listing possible
description and const properties for all channel interrupts is suitable.
> Did you actually test putting this many interrupts into a node?
> AFAICT, any more than 6 will cause complaints.
I tried 12rx and 12tx interrupts in a node, didn't see dtc warning.
so I guess the complaints are from dtb check? I will try to reproduce
them.
>
> Thanks,
> Conor.
next prev parent reply other threads:[~2023-08-10 16:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 16:41 [PATCH net-next v2 00/10] net: stmmac: add new features to xgmac Jisheng Zhang
2023-08-07 16:41 ` Jisheng Zhang
2023-08-07 16:41 ` [PATCH net-next v2 01/10] net: stmmac: correct RX COE parsing for xgmac Jisheng Zhang
2023-08-07 16:41 ` Jisheng Zhang
2023-08-07 16:41 ` [PATCH net-next v2 02/10] net: stmmac: xgmac: add more feature parsing from hw cap Jisheng Zhang
2023-08-07 16:41 ` Jisheng Zhang
2023-08-07 16:41 ` [PATCH net-next v2 03/10] net: stmmac: mdio: enlarge the max XGMAC C22 ADDR to 31 Jisheng Zhang
2023-08-07 16:41 ` Jisheng Zhang
2023-08-07 16:41 ` [PATCH net-next v2 04/10] net: stmmac: enlarge max rx/tx queues and channels to 16 Jisheng Zhang
2023-08-07 16:41 ` Jisheng Zhang
2023-08-07 16:41 ` [PATCH net-next v2 05/10] net: stmmac: reflect multi irqs for tx/rx channels and mac and safety Jisheng Zhang
2023-08-07 16:41 ` Jisheng Zhang
2023-08-07 16:41 ` [PATCH net-next v2 06/10] net: stmmac: xgmac: support per-channel irq Jisheng Zhang
2023-08-07 16:41 ` Jisheng Zhang
2023-08-07 16:41 ` [PATCH net-next v2 07/10] dt-bindings: net: snps,dwmac: add safety irq support Jisheng Zhang
2023-08-07 16:41 ` Jisheng Zhang
2023-08-08 7:28 ` Conor Dooley
2023-08-08 7:28 ` Conor Dooley
2023-08-07 16:41 ` [PATCH net-next v2 08/10] net: stmmac: platform: support parsing safety irqs from DT Jisheng Zhang
2023-08-07 16:41 ` Jisheng Zhang
2023-08-07 16:41 ` [PATCH net-next v2 09/10] dt-bindings: net: snps,dwmac: add per channel irq support Jisheng Zhang
2023-08-07 16:41 ` Jisheng Zhang
2023-08-08 7:39 ` Conor Dooley
2023-08-08 7:39 ` Conor Dooley
2023-08-10 15:59 ` Jisheng Zhang [this message]
2023-08-10 15:59 ` Jisheng Zhang
2023-08-10 16:15 ` Conor Dooley
2023-08-10 16:15 ` Conor Dooley
2023-08-16 15:36 ` Jisheng Zhang
2023-08-16 15:36 ` Jisheng Zhang
2023-08-07 16:41 ` [PATCH net-next v2 10/10] net: stmmac: platform: support parsing per channel irq from DT Jisheng Zhang
2023-08-07 16:41 ` Jisheng Zhang
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=ZNUJSvJi+9QsWhAf@xhacker \
--to=jszhang@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=robh+dt@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.