From: wbarak@gmail.com (Barak Wasserstrom)
To: linux-arm-kernel@lists.infradead.org
Subject: GIC affinity and edge trigger
Date: Thu, 20 Sep 2012 19:22:28 +0300 [thread overview]
Message-ID: <CC811D74.ECFF%wbarak@gmail.com> (raw)
Hello,
I'm currently using linux kernel 2.6.38 with SMP enabled.
I have an interrupt which is a pulse and therefore I set the trigger to
positive edge.
Due to the fact that each CPU sees its own GIC distributor memory space,
only the CPU that executed request_irq has the trigger type set to positive
edge, while the others remain level.
Moreover, gic_set_cpu always defines the GIC distributor target to be CPU0.
So only CPU0 target is enabled + trigger is set to edge only for one CPU and
thus not always do I get the interrupt.
Can you please help me understand what I'm doing wrong, or misunderstand?
Regards,
Barak
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120920/e56f20e7/attachment-0001.html>
next reply other threads:[~2012-09-20 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 16:22 Barak Wasserstrom [this message]
2012-09-24 14:26 ` GIC affinity and edge trigger Marc Zyngier
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=CC811D74.ECFF%wbarak@gmail.com \
--to=wbarak@gmail.com \
--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).