From: Scott Wood <scottwood@freescale.com>
To: Michael Galea <michaelgalea@ruggedcom.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Question on assigning interrupts in a dts
Date: Thu, 12 Jun 2008 12:52:55 -0500 [thread overview]
Message-ID: <48516277.1050509@freescale.com> (raw)
In-Reply-To: <48512EB9.3080307@ruggedcom.com>
Michael Galea wrote:
> Hi All,
> I'm building a dts for a custom 8360 based board. I'm looking at
> the mpc8360_mds and mpc8360_rdk dts files, trying to figure out how the
> UCCs (and all peripherals in general) got the values of their
> "interrupts" properties chosen.
As someone else pointed out, you get the values from the manual. The
second cell of the IPIC interrupt specifier is the level/sense
information (8 == level triggered, active low, 2 == rising edge).
> And is there any relationship between
> the choice of interrupts for ucc1 and the qeic controller..
No. All QE interrupts are multiplexed over either IPIC 32 or IPIC 33.
UCC0 and UCC1 just happen to be QEIC 32 and QEIC 33, respectively.
-Scott
prev parent reply other threads:[~2008-06-12 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 14:12 Question on assigning interrupts in a dts Michael Galea
2008-06-12 17:09 ` Mike Timmons
2008-06-12 20:41 ` Michael Galea
2008-06-12 17:52 ` Scott Wood [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=48516277.1050509@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=michaelgalea@ruggedcom.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).