* Unable to capture device interrupts on ppc440gx?
@ 2005-04-18 16:02 Sanjay Bajaj
2005-04-18 16:14 ` Eugene Surovegin
0 siblings, 1 reply; 3+ messages in thread
From: Sanjay Bajaj @ 2005-04-18 16:02 UTC (permalink / raw)
To: linuxppc-embedded
In the device driver open function, I call request_irq() to register my =
interrupt handler function to a specified IRQ number. It succeeds. But =
when I enable the interrupt (and we can detect the hardware line is =
active) on the hardware, the interrupt handler in NOT invoked. Is there =
something I am missing? Any help or pointers are appreciated.
Sanjay
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Unable to capture device interrupts on ppc440gx?
2005-04-18 16:02 Unable to capture device interrupts on ppc440gx? Sanjay Bajaj
@ 2005-04-18 16:14 ` Eugene Surovegin
0 siblings, 0 replies; 3+ messages in thread
From: Eugene Surovegin @ 2005-04-18 16:14 UTC (permalink / raw)
To: Sanjay Bajaj; +Cc: linuxppc-embedded
On Mon, Apr 18, 2005 at 12:02:52PM -0400, Sanjay Bajaj wrote:
> In the device driver open function, I call request_irq() to register
> my interrupt handler function to a specified IRQ number. It
> succeeds.
> But when I enable the interrupt (and we can detect the hardware line
> is active) on the hardware, the interrupt handler in NOT invoked. Is
> there something I am missing? Any help or pointers are appreciated.
Did you configure polarity and triggering settings for this IRQ
source? If not, look for example at ebony.c (ppc4xx_uic_ext_irq_cfg)
keeping in mind, that Ebony has 440GP CPU. 440GX has 5 additional
IRQ lines.
--
Eugene
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Unable to capture device interrupts on ppc440gx?
@ 2005-04-18 17:02 Sanjay Bajaj
0 siblings, 0 replies; 3+ messages in thread
From: Sanjay Bajaj @ 2005-04-18 17:02 UTC (permalink / raw)
To: Eugene Surovegin; +Cc: linuxppc-embedded
Eugene,
That did help. I was using the Interrupt Line D, whereas hardware is =
generating interrupt on Interrupt Line A. Correcting the IRQ number to =
the one specified in the arch/platforms file captured the interrupt in =
the device driver.
Thanks for the help.
Have a nice day.
Sanjay
-----Original Message-----
From: Eugene Surovegin [mailto:ebs@ebshome.net]
Sent: Monday, April 18, 2005 12:14 PM
To: Sanjay Bajaj
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Unable to capture device interrupts on ppc440gx?
On Mon, Apr 18, 2005 at 12:02:52PM -0400, Sanjay Bajaj wrote:
> In the device driver open function, I call request_irq() to register=20
> my interrupt handler function to a specified IRQ number. It=20
> succeeds.=20
> But when I enable the interrupt (and we can detect the hardware line=20
> is active) on the hardware, the interrupt handler in NOT invoked. Is=20
> there something I am missing? Any help or pointers are appreciated.
Did you configure polarity and triggering settings for this IRQ=20
source? If not, look for example at ebony.c (ppc4xx_uic_ext_irq_cfg)=20
keeping in mind, that Ebony has 440GP CPU. 440GX has 5 additional=20
IRQ lines.
--=20
Eugene
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-04-18 17:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-18 16:02 Unable to capture device interrupts on ppc440gx? Sanjay Bajaj
2005-04-18 16:14 ` Eugene Surovegin
-- strict thread matches above, loose matches on Subject: below --
2005-04-18 17:02 Sanjay Bajaj
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox