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 v3 09/10] dt-bindings: net: snps,dwmac: add per channel irq support
Date: Thu, 10 Aug 2023 23:45:07 +0800 [thread overview]
Message-ID: <ZNUGA+6/K5GJbK4d@xhacker> (raw)
In-Reply-To: <20230809-scabby-cobweb-bb825dffb309@spud>
On Wed, Aug 09, 2023 at 06:38:36PM +0100, Conor Dooley wrote:
> On Thu, Aug 10, 2023 at 12:50:06AM +0800, Jisheng Zhang wrote:
> > The IP supports per channel interrupt, add support for this usage case.
> >
> > Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
>
> I do not see a response to
> <https://lore.kernel.org/all/20230808-clapper-corncob-0af7afa65752@spud/>
> in my mailbox or on lore, nor is there any changes in v3 on this front.
oops, sorry, I didn't mbsync to fetch my inbox before sending out v3, so
I missed your review comments ;)
I will reply in the thread
>
> Thanks,
> Conor.
>
> > ---
> > .../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
> >
> > clocks:
> > minItems: 1
> > --
> > 2.40.1
> >
next prev parent reply other threads:[~2023-08-10 15:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 16:49 [PATCH net-next v3 00/10] net: stmmac: add new features to xgmac Jisheng Zhang
2023-08-09 16:49 ` [PATCH net-next v3 01/10] net: stmmac: correct RX COE parsing for xgmac Jisheng Zhang
2023-08-10 13:45 ` Alexandre TORGUE
2023-08-09 16:49 ` [PATCH net-next v3 02/10] net: stmmac: xgmac: add more feature parsing from hw cap Jisheng Zhang
2023-08-10 13:46 ` Alexandre TORGUE
2023-08-09 16:50 ` [PATCH net-next v3 03/10] net: stmmac: mdio: enlarge the max XGMAC C22 ADDR to 31 Jisheng Zhang
2023-08-10 13:46 ` Alexandre TORGUE
2023-08-09 16:50 ` [PATCH net-next v3 04/10] net: stmmac: enlarge max rx/tx queues and channels to 16 Jisheng Zhang
2023-08-10 14:43 ` Alexandre TORGUE
2023-08-09 16:50 ` [PATCH net-next v3 05/10] net: stmmac: reflect multi irqs for tx/rx channels and mac and safety Jisheng Zhang
2023-08-10 14:50 ` Alexandre TORGUE
2023-08-10 16:02 ` Jisheng Zhang
2023-08-09 16:50 ` [PATCH net-next v3 06/10] net: stmmac: xgmac: support per-channel irq Jisheng Zhang
2023-08-10 14:52 ` Alexandre TORGUE
2023-08-16 15:52 ` Jisheng Zhang
2023-08-09 16:50 ` [PATCH net-next v3 07/10] dt-bindings: net: snps,dwmac: add safety irq support Jisheng Zhang
2023-08-15 21:09 ` Krzysztof Kozlowski
2023-08-09 16:50 ` [PATCH net-next v3 08/10] net: stmmac: platform: support parsing safety irqs from DT Jisheng Zhang
2023-08-10 14:52 ` Alexandre TORGUE
2023-08-09 16:50 ` [PATCH net-next v3 09/10] dt-bindings: net: snps,dwmac: add per channel irq support Jisheng Zhang
2023-08-09 17:38 ` Conor Dooley
2023-08-10 15:45 ` Jisheng Zhang [this message]
2023-08-09 16:50 ` [PATCH net-next v3 10/10] net: stmmac: platform: support parsing per channel irq from DT Jisheng Zhang
2023-08-10 14:57 ` Alexandre TORGUE
2023-08-10 16:09 ` Jisheng Zhang
2023-08-10 16:21 ` 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=ZNUGA+6/K5GJbK4d@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 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).