On 11/02/2015 06:23 AM, Mathieu Rondonneau wrote: > On 15-11-01 07:21 PM, Mathieu Rondonneau wrote: >> On 15-11-01 06:58 PM, Mathieu Rondonneau wrote: >>> On 15-10-31 08:58 PM, Mathieu Rondonneau wrote: >>>> Hi, >>>> >>>> irq handlers registered with devm_request_threaded_irq does not get >>>> triggered when interrupt fires. >>>> >>>> The mmc driver uses this (can not load the rootfs). >>>> Only the IPIPE patch is enabled. >>>> the armctrl chipirq is triggering the .ack handler instead so the >>>> interrupt is happening. >>>> >>>> Any suggestion on where I should look? how is this supported by the >>>> ipipe layer? >>>> >>>> Thanks, >>>> -Mathieu >>> >>> I think I might have answered my own question. >>> Looks like I need to use ipipe_request_irq() instead. >>> >>> Regards, >>> -Mathieu >> mmmm it is not true, it seems we still need a >> ipipe_request_threaded_irq() to call the ackfn, put the handler in the >> queue and wake up the thread once handler is executed. Or user will have >> to move this functionality into their driver's IRQ handler. >> >> It strangely looks like ipipe_request_irq's idea is similar to what >> request_threaded_irq is already doing (delaying IRQ process later). >> >> -Mathieu > Looks like my bigger problem is that the handler_level_irq is not > called. Only the timer handler is called (handler_percpu_devid_irq).
Which may mean that the regular IRQ top half for that interrupt source is not connected to the pipeline. You may want to check whether the irqchip handling that device's IRQs has been made aware of the interrupt pipeline. -- Philippe. _______________________________________________ Xenomai mailing list [email protected] http://xenomai.org/mailman/listinfo/xenomai
