From: Segher Boessenkool <segher@kernel.crashing.org>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: DTS question
Date: Thu, 20 Mar 2008 22:47:57 +0100 [thread overview]
Message-ID: <7aa50e61f9cc57d201706234ecfaf7eb@kernel.crashing.org> (raw)
In-Reply-To: <20080320173302.7075a1d9@lappy.seanm.ca>
> The warp has an AD7414 chip hanging off the I2C bus. This chip can
> raise an interrupt when it crosses a critical threshold.
>
> This interrupt is tied to IRQ2 from the processor.
No it's not. PowerPC has only one interrupt [*]. You probably
mean it is tied to IRQ2 on your "main" interrupt controller?
> What is the best
> way to describe this interrupt in the DTS?
You set the "interrupts" property to contain a description for
this interrupt: likely simply <2 sense>. The exact format (and
the values for "sense") depend on the exact kind of interrupt
controller.
If there is weird interrupt routing, you might need to set an
"interrupt-parent" property as well, pointing to this interrupt
controller.
Segher
next prev parent reply other threads:[~2008-03-20 21:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 21:33 DTS question Sean MacLennan
2008-03-20 21:47 ` Segher Boessenkool [this message]
2008-03-20 21:48 ` Scott Wood
2008-03-20 22:19 ` Sean MacLennan
2008-03-20 22:26 ` Scott Wood
2008-03-21 4:12 ` Sean MacLennan
2008-03-21 4:34 ` Grant Likely
2008-03-21 5:09 ` Sean MacLennan
2008-03-21 7:05 ` David Gibson
2008-03-21 11:35 ` Segher Boessenkool
2008-03-25 22:12 ` David Gibson
2008-03-26 15:32 ` Segher Boessenkool
2008-03-26 23:40 ` David Gibson
2008-03-27 3:42 ` Sean MacLennan
2008-03-21 11:31 ` Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2008-09-02 21:56 Gary Thomas
2008-09-02 23:42 ` David Gibson
2008-09-03 0:14 ` Gary Thomas
2008-09-03 0:25 ` David Gibson
2008-09-02 23:43 ` Scott Wood
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=7aa50e61f9cc57d201706234ecfaf7eb@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.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 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.