[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YBHC6SzXAOSNoQnI@google.com>
Date: Wed, 27 Jan 2021 11:45:45 -0800
From: "dmitry.torokhov@...il.com" <dmitry.torokhov@...il.com>
To: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Cc: "Song Bao Hua (Barry Song)" <song.bao.hua@...ilicon.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"maz@...nel.org" <maz@...nel.org>,
"linuxarm@...neuler.org" <linuxarm@...neuler.org>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 00/12] add IRQF_NO_AUTOEN for request_irq
On Wed, Jan 27, 2021 at 02:49:21PM +0100, gregkh@...uxfoundation.org wrote:
> On Thu, Jan 21, 2021 at 09:38:28PM +0000, Song Bao Hua (Barry Song) wrote:
> > Hi Thomas, Greg, Dmitry, Marc,
> > Any further comment on this new API?
>
> It's not my subsystem, I'll let the irq maintainers handle it :)
Not my subsystem either, but I would like to have this feature
available. I do not like calling irq_set_status_flags() before
request_irq() as at that time we are not ensured of irq ownership, and
using disable_irq() afterwards is indeed awkward.
Thanks.
--
Dmitry
Powered by blists - more mailing lists