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>;
> };
> ...
> [EMAIL PROTECTED] {
> PIC: [EMAIL PROTECTED] {
> #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:[EMAIL PROTECTED] --
> Diplom-Informatiker (FH)
> Linux-Entwicklung
> ----------------------------------------------------------------------------
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
