From: Thomas Gleixner <tglx@linutronix.de>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Bjorn Andersson <bjorn@kryo.se>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Subject: Re: [PATCH] genirq: Introduce irq_read_line()
Date: Sat, 25 Oct 2014 10:34:19 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1410251033270.5308@nanos> (raw)
In-Reply-To: <544AABB8.10302@codeaurora.org>
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
next prev parent reply other threads:[~2014-10-25 18:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 20:23 Bjorn Andersson
2014-09-05 0:14 ` Bjorn Andersson
2014-10-21 9:22 ` Thomas Gleixner
2014-10-21 9:30 ` Arnd Bergmann
2014-10-22 0:14 ` Feng Kan
2014-10-21 9:34 ` Marc Zyngier
2014-10-24 17:31 ` Bjorn Andersson
2014-10-24 17:59 ` Marc Zyngier
2014-10-24 19:42 ` Stephen Boyd
2014-10-25 8:34 ` Thomas Gleixner [this message]
2014-10-27 21:57 ` Stephen Boyd
2014-10-24 23:12 ` Bjorn Andersson
2014-10-25 9:22 ` Marc Zyngier
2014-10-28 15:41 ` Bjorn Andersson
2014-10-28 16:05 ` Marc Zyngier
2014-10-28 17:13 ` Bjorn Andersson
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=alpine.DEB.2.11.1410251033270.5308@nanos \
--to=tglx@linutronix.de \
--cc=adharmap@codeaurora.org \
--cc=bjorn@kryo.se \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=sboyd@codeaurora.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
all inboxes | Powered by JetHome®