* Sricharan R <[email protected]> [140612 04:48]: > From: Nishanth Menon <[email protected]> > > we have currently 2 DMA drivers that try to co-exist. > drivers/dma/omap-dma.c which registers it's own IRQ and is device tree > aware and uses arch/arm/plat-omap/dma.c instance created by > arch/arm/mach-omap2/dma.c to maintain channel usage (omap_request_dma). > > Currently both try to register interrupts and mach-omap2/plat-omap dma.c > attempts to use the IRQ number registered by hwmod to register it's own > interrupt handler. > > Now, there is no reasonable way of static allocating DMA irq in GIC > SPI when we use crossbar. However, since the dma_chan structure is > freed as a result of IRQ not being present due to devm allocation, > maintaining information of channel by platform code fails at a later > point in time when that region of memory is reused. > > So, if hwmod does not indicate an IRQ number, then, assume that > dma-engine will take care of the interrupt handling.
Looks OK to me, applying both into omap-for-v3.17/soc thanks. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
