[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <541eeb3387224fdabc3dcbe6e0ce0db4@hisilicon.com>
Date: Thu, 7 Jan 2021 20:40:00 +0000
From: "Song Bao Hua (Barry Song)" <song.bao.hua@...ilicon.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "tglx@...utronix.de" <tglx@...utronix.de>,
"maz@...nel.org" <maz@...nel.org>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxarm@...neuler.org" <linuxarm@...neuler.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: RE: [PATCH v2] genirq: add IRQF_NO_AUTOEN for request_irq
> -----Original Message-----
> From: Greg KH [mailto:gregkh@...uxfoundation.org]
> Sent: Friday, January 8, 2021 7:58 AM
> To: Song Bao Hua (Barry Song) <song.bao.hua@...ilicon.com>
> Cc: tglx@...utronix.de; maz@...nel.org; linux-input@...r.kernel.org;
> linux-kernel@...r.kernel.org; linuxarm@...neuler.org; Dmitry Torokhov
> <dmitry.torokhov@...il.com>
> Subject: Re: [PATCH v2] genirq: add IRQF_NO_AUTOEN for request_irq
>
> On Tue, Jan 05, 2021 at 03:14:11PM +1300, Barry Song wrote:
> > Many drivers don't want interrupts enabled automatically due to
> > request_irq(). So they are handling this issue by either way of
> > the below two:
> > (1)
> > irq_set_status_flags(irq, IRQ_NOAUTOEN);
> > request_irq(dev, irq...);
> > (2)
> > request_irq(dev, irq...);
> > disable_irq(irq);
> >
> > The code in the second way is silly and unsafe. In the small time
> > gap between request_irq() and disable_irq(), interrupts can still
> > come.
> > The code in the first way is safe though we might be able to do it
> > in the generic irq code.
> >
> > With this patch, drivers can request_irq with IRQF_NO_AUTOEN flag.
> > They will need neither irq_set_status_flags() nor disable_irq().
> > Hundreds of drivers with this problem will be handled afterwards.
> >
> > Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>
> > Signed-off-by: Barry Song <song.bao.hua@...ilicon.com>
>
> Can you also convert some in-kernel drivers to this new api so that we
> can see how this works?
Sure. As the discussion got started from input, so I'll take some
input drivers as examples before moving to other folders.
>
> thanks,
>
> greg k-h
Thanks
Barry
Powered by blists - more mailing lists