From: Scott Wood <scottwood@freescale.com>
To: Bhushan Bharat-R65777 <R65777@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"smitha.vanga@wipro.com" <smitha.vanga@wipro.com>
Subject: Re: IRQ2 and IRQ 3
Date: Tue, 25 Oct 2011 11:14:50 -0500 [thread overview]
Message-ID: <4EA6E07A.50102@freescale.com> (raw)
In-Reply-To: <B8D6CA50DACE9E4AAADE9A4D56FBAAE623CED7@039-SN1MPN1-005.039d.mgd.msft.net>
On 10/18/2011 10:03 AM, Bhushan Bharat-R65777 wrote:
> Hi,
>
> For detail please look at ePAPR specification.
>
> Say i2c interrupt number is 21 then you can try
> "interrupts = <21 8>;" in device tree.
Please read the FSL MPIC binding. For internal interrupts, you need to
add 16 to the number in the manual.
-Scott
next prev parent reply other threads:[~2011-10-25 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 8:06 IRQ2 and IRQ 3 smitha.vanga
2011-10-18 8:58 ` Bhushan Bharat-R65777
2011-10-18 9:05 ` smitha.vanga
2011-10-18 9:10 ` Vineeth
2011-10-18 15:03 ` Bhushan Bharat-R65777
2011-10-25 16:14 ` Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-18 4:05 I2c-cpm driver not working Bhushan Bharat-R65777
2011-10-18 8:05 ` IRQ2 and IRQ 3 smitha.vanga
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=4EA6E07A.50102@freescale.com \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=R65777@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=smitha.vanga@wipro.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).