Hi, * Shah, Hardik <hardik.s...@ti.com> [090106 11:54]: > I have ported the V4L2 driver on top of Tomi's DSS library. DSS library has > requested irq number 25. It is never freeing it. But whenever I get > interrupt from the DSS I get this warning intermittently. > > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > <4>Spurious irq 95: 0xffffffdf, please flush posted write for irq 25 > > > > Please note it's not continuous. Driver is also working fine. Is it > something to do with the latest spurious interrupt patch. > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commitdiff;h=ea153a1765dc754be688013192e8c83c40e008dc > > Is there something to do in the driver to solve this interrupt warning issue.
Interesting. Can you please try adding a read-back of the interrupt status register (or revision register) at the end of the interrupt handler for irq 25? I guess it's INT_24XX_DSS_IRQ, which is the same for 34xx as 24xx? Most likely this spurious interrupt means that the write does not get posted all the way to the interrupt controller for device interrupt handler for irq 25 before irq 25 is unmasked again. Doing a read back in the irq 25 handler after the last write forces the write to get posted. Let me know if that does not help. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
