From: Scott Wood <scottwood@freescale.com>
To: Ran Shalit <ranshalit@gmail.com>
Cc: <linuxppc-dev@lists.ozlabs.org>
Subject: Re: using general IRQs
Date: Mon, 10 Aug 2015 21:29:26 -0500 [thread overview]
Message-ID: <1439260166.4099.14.camel@freescale.com> (raw)
In-Reply-To: <CAJ2oMhJVqph9vb=Q-vbzRRygT+s3wvtm9nVNJ9TLcB_6iQCVcA@mail.gmail.com>
On Mon, 2015-08-10 at 13:40 +0300, Ran Shalit wrote:
> On Mon, Aug 10, 2015 at 10:48 AM, Ran Shalit <ranshalit@gmail.com> wrote:
> > Hello,
> >
> > MPC8349 has general IRQ numbered 0-7,
> > It is required to bind these IRQs with some routine , i.e. they are
> > not used with any specific driver.
> >
> > - Should they be configured as gpios in device tree so that we can use
> > the gpio as irq in linux ? Is there any example ?
> > - After configuration, can the gpios be used in linux using the
> > standard /sys/class/gpio ?
> >
> > Regards,
> > Ran
What do you mean by "general IRQ"? Do you mean external IRQs?
> I am trying to use only IRQ4, so I have tried to configure it as
> following in device tree:
>
> device tree:
>
> intc@0{
> compatible = "intc";
> #address-cells = <1>;
> #size-cells = <0>;
> reg = <0 0x1000>;
> interrupts = <4 0x8>;
> };
>
> But I don't see IRQ4 listed in the interrupt list:
> # cat /proc/interrupts
/proc/interrupts shows virtual interrupts, which do not necessarily
correspond to anything in the device tree. In particular, virtual interrupts
under 16 are reserved for ISA interrupts, and thus any mpic interrupts in
that range will be remapped.
Additionally, putting an interrupt in the device tree does not make it show
up in /proc/interrupts. Only interrupts for which a driver has registered a
handler will show up in /proc/interrupts.
-Scott
next prev parent reply other threads:[~2015-08-11 2:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 7:48 using general IRQs Ran Shalit
2015-08-10 10:40 ` Ran Shalit
2015-08-11 2:29 ` Scott Wood [this message]
2015-08-11 3:45 ` Ran Shalit
2015-08-11 3:47 ` Scott Wood
2015-08-11 6:27 ` Ran Shalit
2015-08-17 10:37 ` Laurentiu Tudor
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=1439260166.4099.14.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ranshalit@gmail.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).