diff options
author | 2019-04-03 19:06:22 +0800 | |
---|---|---|
committer | 2019-04-26 16:51:37 +0530 | |
commit | 2da254cc7908105a60a6bb219d18e8dced03dcb9 (patch) | |
tree | 0d58d112ce9b0c64f73b4f24e0d3b0092891a83c /tools/perf/scripts/python/export-to-postgresql.py | |
parent | dmaengine: axi-dmac: Enable DMA_INTERLEAVE capability (diff) | |
download | wireguard-linux-2da254cc7908105a60a6bb219d18e8dced03dcb9.tar.xz wireguard-linux-2da254cc7908105a60a6bb219d18e8dced03dcb9.zip |
dmaengine: pl330: _stop: clear interrupt status
This patch kill instructs the DMAC to immediately terminate
execution of a thread. and then clear the interrupt status,
at last, stop generating interrupts for DMA_SEV. to guarantee
the next dma start is clean. otherwise, one interrupt maybe leave
to next start and make some mistake.
we can reporduce the problem as follows:
DMASEV: modify the event-interrupt resource, and if the INTEN sets
function as interrupt, the DMAC will set irq<event_num> HIGH to
generate interrupt. write INTCLR to clear interrupt.
DMA EXECUTING INSTRUCTS DMA TERMINATE
| |
| |
... _stop
| |
| spin_lock_irqsave
DMASEV |
| |
| mask INTEN
| |
| DMAKILL
| |
| spin_unlock_irqrestore
in above case, a interrupt was left, and if we unmask INTEN, the DMAC
will set irq<event_num> HIGH to generate interrupt.
to fix this, do as follows:
DMA EXECUTING INSTRUCTS DMA TERMINATE
| |
| |
... _stop
| |
| spin_lock_irqsave
DMASEV |
| |
| DMAKILL
| |
| clear INTCLR
| mask INTEN
| |
| spin_unlock_irqrestore
Signed-off-by: Sugar Zhang <sugar.zhang@rock-chips.com>
Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions