ARM: OMAP2+: DMA: remove requirement of irq for platform-dma driver
authorNishanth Menon <nm@ti.com>
Thu, 12 Jun 2014 11:45:22 +0000 (17:15 +0530)
committerTony Lindgren <tony@atomide.com>
Tue, 22 Jul 2014 06:32:51 +0000 (23:32 -0700)
commit76be4a54157ab0059fb29d8d516db46d239812e2
tree434db5329e5a6facbc1ca84bfac6c20daf9c7972
parent3db53918e306d3960bf9e12eea8b2fd3f7d0fd62
ARM: OMAP2+: DMA: remove requirement of irq for platform-dma driver

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.

Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
arch/arm/mach-omap2/dma.c
arch/arm/plat-omap/dma.c
include/linux/omap-dma.h