summaryrefslogtreecommitdiffstats
path: root/drivers/dma/qcom
diff options
context:
space:
mode:
authorRobin Gong <yibin.gong@nxp.com>2019-06-21 16:23:06 +0800
committerVinod Koul <vkoul@kernel.org>2019-07-05 13:15:37 +0530
commit3f93a4f297961c12bb17aa16cb3a4d1291823cae (patch)
treeee2d983526825640a9fb6485a6116516b11f5e09 /drivers/dma/qcom
parent2b8066c3deb9140fdf258417a51479b2aeaa7622 (diff)
downloadlinux-3f93a4f297961c12bb17aa16cb3a4d1291823cae.tar.bz2
dmaengine: imx-sdma: remove BD_INTR for channel0
It is possible for an irq triggered by channel0 to be received later after clks are disabled once firmware loaded during sdma probe. If that happens then clearing them by writing to SDMA_H_INTR won't work and the kernel will hang processing infinite interrupts. Actually, don't need interrupt triggered on channel0 since it's pollling SDMA_H_STATSTOP to know channel0 done rather than interrupt in current code, just clear BD_INTR to disable channel0 interrupt to avoid the above case. This issue was brought by commit 1d069bfa3c78 ("dmaengine: imx-sdma: ack channel 0 IRQ in the interrupt handler") which didn't take care the above case. Fixes: 1d069bfa3c78 ("dmaengine: imx-sdma: ack channel 0 IRQ in the interrupt handler") Cc: stable@vger.kernel.org #5.0+ Signed-off-by: Robin Gong <yibin.gong@nxp.com> Reported-by: Sven Van Asbroeck <thesven73@gmail.com> Tested-by: Sven Van Asbroeck <thesven73@gmail.com> Reviewed-by: Michael Olbrich <m.olbrich@pengutronix.de> Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'drivers/dma/qcom')
0 files changed, 0 insertions, 0 deletions