From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: GIC affinity and edge trigger
Date: Mon, 24 Sep 2012 15:26:29 +0100 [thread overview]
Message-ID: <50606D95.8070109@arm.com> (raw)
In-Reply-To: <CC811D74.ECFF%wbarak@gmail.com>
On 20/09/12 17:22, Barak Wasserstrom wrote:
> 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.
This seem to imply that your interrupt is a PPI, and not a SPI. If this
is the case, you cannot use request_irq on such an interrupt. 2.6.38 is
pretty ancient though, and doesn't have any support for
request_percpu_irq and co. How are you configuring/requesting this
interrupt?
> Moreover, gic_set_cpu always defines the GIC distributor target to be CPU0.
For a PPI, the concept of "target" is pretty minimal, and is always the
CPU this PPI is connected to.
> 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?
Please clarify whether you're using a PPI or an SPI. The above is not
clear enough to give you a straight answer.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2012-09-24 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 16:22 GIC affinity and edge trigger Barak Wasserstrom
2012-09-24 14:26 ` Marc Zyngier [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=50606D95.8070109@arm.com \
--to=marc.zyngier@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.