From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: [Q] GIC : IRQ_TYPE_LEVEL_LOW interrupts
Date: Wed, 13 Apr 2011 13:17:17 +0530 [thread overview]
Message-ID: <BANLkTimrxA0-U65Tw208tc1Mqz5ZGa8X9Q@mail.gmail.com> (raw)
In-Reply-To: <4DA4A1E2.9090304@ti.com>
On Wed, Apr 13, 2011 at 00:32, Santosh Shilimkar
<santosh.shilimkar@ti.com> wrote:
> As part of the commit 5c0c1f08a (gic: implement set_type)
> change, I see that you are ignoring interrupts which
> are of LOW_LEVEL type. Why is that ?
>
> There are interrupts of LOW_LEVEL type on OMAP and this
> change break those.
Please see the discussion on an earlier, similar patch:
https://patchwork.kernel.org/patch/75509/. The discussion did
not move further at that time and the "rather easy" solution
mentioned there was implemented.
The GIC spec seems to only talk about rising-edge and active
high:
http://infocenter.arm.com/help/topic/com.arm.doc.ihi0048a/CACCAGCF.html
prev parent reply other threads:[~2011-04-13 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 19:02 [Q] GIC : IRQ_TYPE_LEVEL_LOW interrupts Santosh Shilimkar
2011-04-13 7:47 ` Rabin Vincent [this message]
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=BANLkTimrxA0-U65Tw208tc1Mqz5ZGa8X9Q@mail.gmail.com \
--to=rabin@rab.in \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).