request_irq issue

request_irq issue

[Laxmikant Rashinkar]

[-- Attachment #1: Type: text/plain, Size: 416 bytes --]

Hi,

I have a MPC8347 based board that runs linux-2.6.15.4 and 2.6.27.1.

With the older Linux, my driver is able to successfully request_irq() interrupts 17, 18, 19, 20, 21, 22, 23 & 48.

But with the newer linux, request_irq() works only for 17, 18 & 19. cat /proc/interrupts shows that none of the interrupts above are in use.
Any pointers on why request_irq() is behaving thus?

thanks for your help
LK



      

[-- Attachment #2: Type: text/html, Size: 650 bytes --]

Re: request_irq issue

[Ben Warren]

[-- Attachment #1: Type: text/plain, Size: 705 bytes --]

On Tue, Nov 4, 2008 at 7:38 PM, Laxmikant Rashinkar <lk.atwork@yahoo.com>wrote:

> Hi,
>
> I have a MPC8347 based board that runs linux-2.6.15.4 and 2.6.27.1.
>
> With the older Linux, my driver is able to successfully request_irq()
> interrupts 17, 18, 19, 20, 21, 22, 23 & 48.
>
> But with the newer linux, request_irq() works only for 17, 18 & 19. cat
> /proc/interrupts shows that none of the interrupts above are in use.
> Any pointers on why request_irq() is behaving thus?
>
> thanks for your help
> LK
>
> Search the mailing list archive.  I've posted sample code for how to enable
external interrupts, but it was probably around 2.6.19 time.  I imagine the
same issues still exist.

regards,
Ben

[-- Attachment #2: Type: text/html, Size: 1184 bytes --]

Re: request_irq issue

[Arnd Bergmann]

On Wednesday 05 November 2008, Laxmikant Rashinkar wrote:
> But with the newer linux, request_irq() works only for 17, 18 & 19. cat /proc/interrupts shows that none of the interrupts above are in use.
> Any pointers on why request_irq() is behaving thus?

Note that you need to get the raw IRQ number from the device tree now,
and map it to a virtual IRQ number using irq_of_parse_and_map.
That is the number you pass to request_irq().

	Arnd <><