Hi, On Mon, Jan 05, 2015 at 08:01:22PM -0600, Felipe Balbi wrote: > On Tue, Jan 06, 2015 at 01:16:21AM +0200, Aaro Koskinen wrote: > > I did some debugging and it seems the "In-band Error" > > occurs when omap_system_dma_probe() is being run, specifically when > > the interrupt is enabled. I believe the "DMA" interrupt it's trying > > set up is completely wrong: > > > > 28: 0 GPIO 2 DMA > > > > GPIO 2?! Where is that coming from? > > heh, it's probably the linux number used ended up mapping to another irq > domain. Can you add this debugging patch and report dmesg ? Post-commit: [ 0.208251] omap_dma_system omap_dma_system.0: legacy DMA IRQ 28 [ 0.216125] omap-dma-engine 48056000.dma-controller: dmaengine IRQ 22 22: 5 INTC 13 omap-dma-engine 28: 0 GPIO 2 DMA Pre-commit: [ 0.208557] omap_dma_system omap_dma_system.0: legacy DMA IRQ 28 [ 0.216461] omap-dma-engine 48056000.dma-controller: dmaengine IRQ 29 28: 0 INTC 12 DMA 29: 5 INTC 13 omap-dma-engine > Note that I need one log post commit and another log pre commit. If any > of the IRQ numbers change, if means that irq_domain_add_linear() ended > up changing IRQ start and we would need some trick to grab the correct > IRQ number again. So looks like static OMAP_INTC_START cannot be used anymore, but hwmod data is full of these? mach-omap2/omap_hwmod_2xxx_3xxx_ipblock_data.c: { .name = "0", .irq = 12 + OMAP_INTC_START, }, /* INT_24XX_SDMA_IRQ0 */ A. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html