[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1410251033270.5308@nanos>
Date: Sat, 25 Oct 2014 10:34:19 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Stephen Boyd <sboyd@...eaurora.org>
cc: Marc Zyngier <marc.zyngier@....com>,
Bjorn Andersson <bjorn@...o.se>,
Linus Walleij <linus.walleij@...aro.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Abhijeet Dharmapurikar <adharmap@...eaurora.org>
Subject: Re: [PATCH] genirq: Introduce irq_read_line()
On Fri, 24 Oct 2014, Stephen Boyd wrote:
> On 10/24/2014 10:59 AM, Marc Zyngier wrote:
> > Hi Bjorn,
> >
> > On 24/10/14 18:31, Bjorn Andersson wrote:
> >>
> >> Stephen Boyd talked about the need to be able to mask/unmask interrupts from
> >> client code in the Qualcomm platform as well - most likely to block wakeup
> >> sources(?)
> > What's wrong with irq_disable?
>
> The problem is irq_disable() is lazy and doesn't actually disable the
> interrupt.
Nothing prevents you from adding your own irq_disable() callback for
those interrupts. Just the default is lazy.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists