linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Suvidh Kankariya <suvidh.kankariya@ntigo.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: adding external interrupt support for MPC8313e bsp
Date: Thu, 22 May 2008 16:21:39 -0500	[thread overview]
Message-ID: <4835E3E3.4050004@freescale.com> (raw)
In-Reply-To: <4835DA6E.2020709@ntigo.com>

Suvidh Kankariya wrote:
> I have mpc8313e local bus connected to a external UART. and the 
> interrupt is connected to EXT_INT2.
> I am able to communicate to UART if I disable IRQ i.e IRQ = 0 in port 
> structure.
> 
> I am not able to understand how to tell kernel to use external IRQ -2.
> Should I put the external interrupts in device tree and if so how?

Yes, you should put them in the device tree in the interrupts property 
of the node corresponding to the device that is using the interrupt. 
The first cell should be 18 (decimal) for IRQ2 (see the IPIC section of 
the user manual for other external IRQs).  The second cell is defined 
the same as the PQ1/CPM2 PIC described in 
Documentation/booting-without-of.txt (2 for falling edge, 8 for active low).

> or can I use the interrupt directly in the driver  and in that case do I 
> need to map the interrupt.

Yes, if you don't put it in the device tree you need to call 
irq_create_mapping().  Using the device tree is recommended.

-Scott

      reply	other threads:[~2008-05-22 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 20:41 adding external interrupt support for MPC8313e bsp Suvidh Kankariya
2008-05-22 21:21 ` 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=4835E3E3.4050004@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=suvidh.kankariya@ntigo.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).