Re: DTS device tree node for dual port RAM

[Grant Likely <grant.likely@secretlab.ca>]

On Thu, Mar 12, 2009 at 9:19 AM, EXTERNAL Lange Matthias (AA-DGW/ENG1)
<Matthias.Lange@beissbarth.com> wrote:
>> What hardware irq# are you using? =A0See 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. Tha=
t's why I was defining the interrupts property to <0 0 0>. So my device tre=
e node now looks like this

Okay, good.  I just wanted to make sure.

> dpram@40000000 {
> =A0 =A0 =A0 =A0compatible =3D "beissbarth,orion-dpram";
> =A0 =A0 =A0 =A0interrupts =3D <0 0 0>;
> =A0 =A0 =A0 =A0interrupt-parent =3D <&mpc5200_pic>;
> };

This is unrelated to your question, but I'm wondering why you don't
have a reg property in your node.

> 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 dev=
ice.

That is the easiest way, yes.  Actually, all you need to call
irq_of_parse_and_map() is a pointer to the device_node which can be
obtained by directly searching the tree.  However, writing an
of_platform driver is a better way to get the device_node in this
case.

g.

--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.