Freescale Interrupt enabling

Freescale Interrupt enabling

[Alan Bennett]

We were developing with Linux 2.6.10 and a Planetcore boot loader,
however, recent work has us up and running with 2.6.23+ and U-boot
1.2.0.  However, we are now running into a few challenges regarding
the differences.

Our driver writer's code isn't functioning, but it was with 2.6.10 and
planet core.  The best I can tell is that the default interrupt
controller configuration isn't where it was in the planetcore/2.6.10
version.

for example, let's look at enabling timer1 / interrupt number 12

simple description.
	       timer1 {
	 	       name = "timer1";
 		       compatible = "fsl,mpc8248_timer";
		       interrupts = <c 8>;
		       interrupt-parent = <&PIC>;

What should be done to consume the above description in the device
tree, program the SIU and configure the irq for request?  I'm looking
through the existing drivers to get a feel, but both the enets and the
uarts are overly complex for the simple task of enabling a timer, as
our driver code already works with the irq on other linux
kernels/bootloaders.

-Alan

Re: Freescale Interrupt enabling

[David Gibson]

On Thu, Oct 18, 2007 at 08:41:35AM -0600, Alan Bennett wrote:
> We were developing with Linux 2.6.10 and a Planetcore boot loader,
> however, recent work has us up and running with 2.6.23+ and U-boot
> 1.2.0.  However, we are now running into a few challenges regarding
> the differences.
> 
> Our driver writer's code isn't functioning, but it was with 2.6.10 and
> planet core.  The best I can tell is that the default interrupt
> controller configuration isn't where it was in the planetcore/2.6.10
> version.
> 
> for example, let's look at enabling timer1 / interrupt number 12
> 
> simple description.
> 	       timer1 {
> 	 	       name = "timer1";
>  		       compatible = "fsl,mpc8248_timer";
> 		       interrupts = <c 8>;
> 		       interrupt-parent = <&PIC>;

Device tree nodes should really describe an actual device, not just
some random floating interrupt.  You need to work out what device this
interrupt actually belongs to, and describe that.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson