On Mon, Jan 25, 2010 at 06:16:08PM +0100, Julian Fuchs wrote: > being aware of the risk to bother some people here I would > nevertheless really appreciate your help with the following issue: > > Is there any difference in the request_irq() function call in > comparison to the one in the normal kernel? > > I'm trying to run > > request_irq(irq, interrupt_handler, IRQF_SHARED | IRQF_DISABLED | > IRQF_NODELAY, MODULE_IDENT, &stage) > > on 2.6.31.6-rt19 but it doesn't call interrupt_handler() when an > interrupt is received. > > In the plain kernel 2.6.31 it works with this call: > > request_irq(irq, interrupt_handler, IRQF_SHARED | IRQF_DISABLED, > MODULE_IDENT, &stage) Did you try with IRQF_NODELAY on vanilla and without it in rt? Are you sure the irq fires in rt? Does your interrupt appear in /proc/interrupts? What platform are you working on? Do you can send the code of a minimal example? Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ | -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
