[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f725ba58-e94b-5df7-2efe-70b18382ba2d@microchip.com>
Date: Tue, 19 Sep 2023 11:04:14 +0000
From: <Parthiban.Veerasooran@...rochip.com>
To: <andrew@...n.ch>
CC: <davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
<pabeni@...hat.com>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
<corbet@....net>, <Steen.Hegelund@...rochip.com>,
<rdunlap@...radead.org>, <horms@...nel.org>,
<casper.casan@...il.com>, <netdev@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-doc@...r.kernel.org>, <Horatiu.Vultur@...rochip.com>,
<Woojung.Huh@...rochip.com>, <Nicolas.Ferre@...rochip.com>,
<UNGLinuxDriver@...rochip.com>, <Thorsten.Kummermehr@...rochip.com>
Subject: Re: [RFC PATCH net-next 2/6] net: ethernet: add mac-phy interrupt
support with reset complete handling
Hi Andrew,
On 13/09/23 7:49 am, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
>> Ok. If I understand correctly, I have to use devm_request_threaded_irq()
>> instead of devm_request_irq() and let the thread handler registered with
>> the devm_request_threaded_irq() function to perform interrupt activity
>> directly?
>
> Yes. I've not looked at all the patches yet, but if the work queue is
> not used for anything else, you should be able to remove it, and let
> the IRQ core handle all the threading for you.
Sure, will implement it. Thanks.
Best Regards,
Parthiban V
>
> Andrew
>
Powered by blists - more mailing lists