From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Bennett <embedded@akb.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: request_irq fails to get interrupt 12
Date: Tue, 23 Oct 2007 06:33:44 +1000 [thread overview]
Message-ID: <1193085224.6745.102.camel@pasglop> (raw)
In-Reply-To: <bfa0697f0710221255ubbe8c91pa09640f9b9cd0775@mail.gmail.com>
On Mon, 2007-10-22 at 13:55 -0600, Alan Bennett wrote:
> Ok, so what does it take to expose an interrupt vector on a pq2 PIC??
> -Alan
Also, if it's the default PIC or if you happen to have the PIC struct
irq_host pointer at hand, a quickish way for internal device interrupts
is to directly call irq_create_mapping() though using the device-tree is
nicer.
Ben.
> Current:
> /
> localbus{
> ...
> fundevice1 {
> interrupts = <c 8>;
> interrupt-parent = <&PIC>;
> };
> ...
> soc@e0000000 {
> PIC: interrupt-controller@10c00 {
> #interrupt-cells = <2>;
> interrupt-controller;
> reg = <10c00 80>;
> compatible = "fsl,mpc8248-pic", "fsl,pq2-pic";
> };
> Is the above device tree enough on its own?
> Do I have to write some platform code beyond:
> static void __init ep8248_pic_init(void)
> {
> struct device_node *np = of_find_compatible_node(NULL, NULL, "fsl,pq2-pic");
> if (!np) {
> printk(KERN_ERR "PIC init: can not find cpm-pic node\n");
> return;
> }
>
> cpm2_pic_init(np);
> of_node_put(np);
> }
>
> -Alan
>
> Hello,
>
> > Freescale experts. Why on earth can't I request the IRQ for Timer1?
>
> Please consule my question on [1] and the answers.
>
> [1] http://ozlabs.org/pipermail/linuxppc-dev/2007-September/042061.html
>
> bye
> Silvio Fricke
>
> --
> -- S. Fricke ----------------------------- MAILTO:silvio.fricke@gmail.com --
> Diplom-Informatiker (FH)
> Linux-Entwicklung
> ----------------------------------------------------------------------------
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2007-10-22 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 19:55 request_irq fails to get interrupt 12 Alan Bennett
2007-10-22 20:33 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-22 16:47 Alan Bennett
2007-10-22 17:21 ` S. Fricke
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=1193085224.6745.102.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=embedded@akb.net \
--cc=linuxppc-dev@ozlabs.org \
/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).