Re: devicetree and IRQ7 mapping for T1042(mpic)

[Joakim Tjernlund <joakim.tjernlund@transmode.se>]

On Wed, 2015-10-14 at 19:11 -0500, Scott Wood wrote:
> On Wed, 2015-10-14 at 19:37 +0000, Joakim Tjernlund wrote:
> > I am trying to figure out how to describe/map external IRQ7 in the=20
> > devicetree.
> >=20
> > Basically either IRQ7 to be left alone by Linux(becase u-boot already s=
et=20
> > it up)
> > or map IRQ7 to sie 0(MPIC_EILR7=3D0xf0) and prio=3D0xf(MPIC_EIVPR7=3D0x=
4f0000)
> >=20
> > There is no need for SW handler because IRQ7 will be routed to the DDR=
=20
> > controller
> > and case an automatic Self Refresh just before CPU reset.
> >=20
> > I cannot figure out how to do this. Any ideas?
> >=20
> > If not possible from devicetree, then can one do it from board code?
>=20
> The device tree describes the hardware.  Priority is configuration, and t=
hus=20
> doesn't belong there.  You can call mpic_irq_set_priority() from board co=
de.

Right.

>=20
> Likewise, the fact that you want to route irq7 to sie0 is configuration, =
not=20
> hardware description.  At most, the device tree should describe is what i=
s=20
> connected to each sie output.  There's no current Linux support for routi=
ng=20
> an interrupt to sie or anything other than "int".

That explains why I could not find any mpic function for that ..

I found mpic dev. trees property "protected-sources" which might do what I =
want, just
leave the the irq alone but I cannot figure out what value to write there.
Could you give me any example how to calculate dev. tree irq number for IRQ=
7?

The mpic.txt mentions "Interrupt Source Configuration Registers" but google=
 did
not turn up anything useful for me.

 Jocke=