> -----Original Message-----
> From:
> [email protected]
> [mailto:linuxppc-dev-bounces+matthias.lange=beissbarth....@ozl
> abs.org] On Behalf Of Grant Likely
> Sent: Thursday, March 12, 2009 2:32 PM
> To: EXTERNAL Lange Matthias (AA-DGW/ENG1)
> Cc: [email protected]
> Subject: Re: DTS device tree node for dual port RAM
>
> On Thu, Mar 12, 2009 at 5:24 AM, EXTERNAL Lange Matthias (AA-DGW/ENG1)
> <[email protected]> wrote:
> > Hi,
[...]
>
> > interrupts = <0 0 0>;
>
> What hardware irq# are you using? See this link for a description of
> what the interrupts property should look like for external IRQs:
I am using hardware irq# 0 which is wired to the critical input line. That's
why I was defining the interrupts property to <0 0 0>. So my device tree node
now looks like this
dp...@40000000 {
compatible = "beissbarth,orion-dpram";
interrupts = <0 0 0>;
interrupt-parent = <&mpc5200_pic>;
};
If I am understanding it correctly I now need to implement a OF platform driver
in which I can use irq_of_parse_and_map() to get the virq for my device.
Regards,
Matthias Lange.
>
> http://patchwork.ozlabs.org/patch/11349/
>
> To use this property, the irq_of_parse_and_map() function will
> translate from the device tree to a Linux IRQ number.
>
> > interrupt-parent = <&mpc5200_pic>;
>
> You probably also want a reg = <0 0 0x00400000>; property for mapping
> the address range.
>
> > };
> > };
> >
> > What am I doing wrong? What am I missing?
> >
> > Thanks,
> > Matthias Lange.
> > _______________________________________________
> > Linuxppc-dev mailing list
> > [email protected]
> > https://ozlabs.org/mailman/listinfo/linuxppc-dev
> >
>
>
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> _______________________________________________
> Linuxppc-dev mailing list
> [email protected]
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev
