From: Conor Dooley <conor@kernel.org>
To: Selvamani Rajagopal <Selvamani.Rajagopal@onsemi.com>
Cc: "Parthiban.Veerasooran@microchip.com"
<Parthiban.Veerasooran@microchip.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
Piergiorgio Beruto <Pier.Beruto@onsemi.com>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Conor.Dooley@microchip.com" <Conor.Dooley@microchip.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH net v3 2/2] dt-bindings: net: updated interrupt type to be active low, level triggered
Date: Thu, 4 Jun 2026 17:36:15 +0100 [thread overview]
Message-ID: <20260604-swimwear-garnet-3eb092e6fda7@spud> (raw)
In-Reply-To: <CY8PR02MB9249E607ACBF3A05AB83ABF683102@CY8PR02MB9249.namprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1992 bytes --]
On Thu, Jun 04, 2026 at 03:21:47PM +0000, Selvamani Rajagopal wrote:
> > Subject: Re: [PATCH net v3 2/2] dt-bindings: net: updated interrupt type to be active low,
> > level triggered
> >
> > Hi Conor & Selvamani,
To be clear, my angle here is making sure that the microchip device is
not deviant from the spec. I don't know or care about this hardware in
particular.
I just made the assumption that what was in the example worked, and
wanted clarification that what the example was changed to actually
reflected something else that worked on the hardware in question before
I gave an ack. I'm a dt-binding maintainer, not someone with knowledge
of these devices.
> >
> [.]
> > One possible alternative could be to use a threaded IRQ handler with
> > IRQF_ONESHOT, where the IRQ line is disabled until the handler
> > completes, and sleeping is allowed. In that case, we could perform the
> > SPI transfer in the threaded handler to send the data header and
> > deassert the interrupt, while deferring the remaining work to a separate
> > kthread (the current SPI thread). However, I have not yet tried this
> > implementation, so I cannot comment on its behavior or effectiveness
> > without implementing and testing it.
>
> I can test this in my setup.
>
> >
> > I may be missing something here and am trying to clarify my
> > understanding. I am also curious why this issue reproduces on our system
> > but does not appear in Selvamani’s setup with an active‑low level
> > interrupt configuration. If possible, could you share details of your
> > setup and how the testing is being performed?
>
> My setup is similar to yours. We have Raspberry Pi boards (P-4 & Pi-5) connected
> to our MAC-PHY evaluation board. As you could see in my patch submissions,
> there are no changes to oa_tc6.c in the way interrupts are handled.
>
> >
> > Best regards,
> > Parthiban V
> > >
> > >>
> > >> Cheers,
> > >> Conor.
> > >>
> > >>>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-06-04 16:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 16:07 [PATCH net v3 0/2] Resubmitting with cover-letter and threaded patch series Selvamani Rajagopal via B4 Relay
2026-06-01 16:07 ` [PATCH net v3 1/2] net: ethernet: oa_tc6: Interrupt is active low, level triggered Selvamani Rajagopal via B4 Relay
2026-06-02 16:07 ` sashiko-bot
2026-06-01 16:07 ` [PATCH net v3 2/2] dt-bindings: net: updated interrupt type to be " Selvamani Rajagopal via B4 Relay
2026-06-02 16:07 ` sashiko-bot
2026-06-02 16:42 ` Conor Dooley
2026-06-02 17:36 ` Selvamani Rajagopal
2026-06-03 15:08 ` Conor Dooley
2026-06-04 6:29 ` Parthiban.Veerasooran
2026-06-04 7:08 ` Nicolai Buchwitz
2026-06-04 15:21 ` Selvamani Rajagopal
2026-06-04 16:36 ` Conor Dooley [this message]
2026-06-04 17:00 ` Andrew Lunn
2026-06-08 4:13 ` Parthiban.Veerasooran
2026-06-08 4:44 ` Selvamani Rajagopal
2026-06-08 7:15 ` Andrew Lunn
2026-06-08 15:04 ` Selvamani Rajagopal
2026-06-09 9:15 ` Parthiban.Veerasooran
2026-06-09 15:40 ` Selvamani Rajagopal
2026-06-09 20:02 ` Selvamani Rajagopal
2026-06-11 13:01 ` Parthiban.Veerasooran
2026-06-11 14:22 ` Selvamani Rajagopal
2026-06-11 21:59 ` Selvamani Rajagopal
2026-06-12 12:43 ` Parthiban.Veerasooran
2026-06-04 13:19 ` [PATCH net v3 0/2] Resubmitting with cover-letter and threaded patch series Paolo Abeni
2026-06-04 14:51 ` Selvamani Rajagopal
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=20260604-swimwear-garnet-3eb092e6fda7@spud \
--to=conor@kernel.org \
--cc=Conor.Dooley@microchip.com \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=Pier.Beruto@onsemi.com \
--cc=Selvamani.Rajagopal@onsemi.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox