From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Wolfgang Grandegger" <wg@grandegger.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: interrupt cells on mpc5200
Date: Wed, 10 Sep 2008 13:39:34 -0400 [thread overview]
Message-ID: <9e4733910809101039l39eed2cdl43b2004bee334687@mail.gmail.com> (raw)
In-Reply-To: <48C7FBCD.10803@grandegger.com>
On Wed, Sep 10, 2008 at 12:54 PM, Wolfgang Grandegger <wg@grandegger.com> wrote:
> Jon Smirl wrote:
>> mpc5200 interrupts have three cells in the device tree. How are these
>> interpreted?
>> Middle one is the interrupt number. Last one seems to always be zero.
>> What does the first one do, edge/level?
>>
>> I searched through /Documentation and could find anything about three
>> cells for interrupts.
>>
>> I understand the first one for gpio_wkup on interrupt 8. How does a
>> gpio_wkup generate an interrupt on interrupt 3?
>>
>> gpio_wkup: gpio-wkup@c00 {
>> compatible = "fsl,mpc5200b-gpio-wkup","fsl,mpc5200-gpio-wkup";
>> reg = <0xc00 0x40>;
>> interrupts = <0x1 0x8 0x0 0x0 0x3 0x0>;
>> interrupt-parent = <&mpc5200_pic>;
>> gpio-controller;
>> #gpio-cells = <2>;
>> };
>
> See
> http://lxr.linux.no/linux+v2.6.26.5/Documentation/powerpc/mpc52xx-device-tree-bindings.txt#L263
Why was I too blind to see that file? So there must be someway to turn
a gpio_wkup into a critical interrupt which causes the interrupt 3
which is a feature I don't need.
Any hints on a good way to measure the length of pulses? They are
between 500us and 2ms long. I was thinking of using an interrupt on
the leading edge, starting a timer, and then flipping the gpio to
cause an interrupt on the trailing edge. I don't need extreme
accuracy.
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2008-09-10 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 16:40 interrupt cells on mpc5200 Jon Smirl
2008-09-10 16:54 ` Wolfgang Grandegger
2008-09-10 17:39 ` Jon Smirl [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=9e4733910809101039l39eed2cdl43b2004bee334687@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=wg@grandegger.com \
/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).