From: "Kári Davíðsson" <kari.davidsson@marel.is>
To: <linuxppc-embedded@ozlabs.org>
Subject: External interrupt type?
Date: Fri, 14 Mar 2008 19:05:36 -0000 [thread overview]
Message-ID: <1205521536.28630.4.camel@marel2693> (raw)
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Hello,
I am dealing with external interrupts on an custom board of the
mpc5200b. Kernel is 2.6.24 from kernel.org.
I can declare the interrupt in the dts for the board and the
control register is set correctly, i.e. the correct external interrupt
is enabled.
On the other hand the type is ignored and is always level interrupt
active low.
Is this intended behaviour?
How can I pass in the interrupt type from the dts to the kernel?
I need to have the interrupt as edge interrupt, rising edge type?
rg
kd
[-- Attachment #2: Type: text/html, Size: 972 bytes --]
next reply other threads:[~2008-03-14 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 19:05 Kári Davíðsson [this message]
2008-03-15 11:54 ` External interrupt type? Kári Davíðsson
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=1205521536.28630.4.camel@marel2693 \
--to=kari.davidsson@marel.is \
--cc=kari.davidsson@marel.com \
--cc=linuxppc-embedded@ozlabs.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).