summaryrefslogtreecommitdiff
path: root/drivers/dma/mediatek
diff options
context:
space:
mode:
authorLars-Peter Clausen <lars@metafoo.de>2021-10-25 10:54:26 +0300
committerVinod Koul <vkoul@kernel.org>2021-10-28 20:23:54 +0300
commita34da7ef9a8c2b89ddb84689562f3d2b48a4e588 (patch)
tree00f71d23ab07b607c2f3b9eba465b3fae5e25bd4 /drivers/dma/mediatek
parentd191a9abc02f1f59bfb3b2349d30cb5534dc0fd9 (diff)
downloadlinux-a34da7ef9a8c2b89ddb84689562f3d2b48a4e588.tar.xz
dmaengine: altera-msgdma: Correctly handle descriptor callbacks
DMA clients can provide one of two types of callbacks. For this reason dmaengine drivers should not directly invoke `callback`, but always use dmaengine_desc_callback_invoke(). This makes sure that both types of callbacks are handled correctly. The altera-msgdma driver currently doesn't do this and only handles the `callback` type callback. If the client used the `callback_result` type callback it will not be called. Fix this by switching to `dmaengine_desc_callback_valid()` and `dmaengine_desc_callback_invoke()`. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Link: https://lore.kernel.org/r/20211025075428.2094-1-lars@metafoo.de Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'drivers/dma/mediatek')
0 files changed, 0 insertions, 0 deletions