Hi Florian,
It is not clear to me whether this secondary cevt is also a r4k-cevt
device, or if it is something else? If the IRQ is shared, is there any
way to differentiate the ralink cevt from the r4k cevt, such that both
could request the same irq with the IRQF_SHARED flag?
IRQF_SHARED | IRQF_TIMER is not allowed as a combination.
It looks to me like you are moving the irq setup later just to ensure
that your ralink clockevent device has been registered before and has
set cp0_timer_irq_installed when the set_mode() r4k clockevent device
runs, such that it won't register the same IRQ that your platforms
uses. If that it the case, cannot you just ensure that you run your
cevt device registration before mips_clockevent_init() is called?
i dont like relying on the order in which the modules get loaded.
the actual problem is not the irq sharing but that the cevt-r4k
registers the irq when the cevt is registered and not when it is
activated. i believe that the patch fixes this problem
John
