diff options
| author |   Chanho Park <chanho61.park@samsung.com> | 2022-06-27 10:38:45 +0900 |
|---|---|---|
| committer |   Mark Brown <broonie@kernel.org> | 2022-06-27 23:26:54 +0100 |
| commit | 82295bc0d192d7e35e0568b18ca66da2c3058fd5 (patch) | |
| tree | 210c03b0361dcc34f39a283de8fa3b9fee0c6954 /tools/perf/scripts/python/call-graph-from-sql.py | |
| parent | spi: synquacer: Add missing clk_disable_unprepare() (diff) | |
| download | linux-dev-82295bc0d192d7e35e0568b18ca66da2c3058fd5.tar.xz linux-dev-82295bc0d192d7e35e0568b18ca66da2c3058fd5.zip | |
spi: s3c64xx: move dma_release_channel to unprepare
This fixes the sequence of dma_release_channel.
Since commit f52b03c70744 ("spi: s3c64xx: requests spi-dma channel only
during data transfer"),
dma_release_channel has been located in the s3c64xx_spi_transfer_one
but this makes invalid return of can_dma callback.
__spi_unmap_msg will check whether the request is requested by dma or
not via can_dma callback. When it is calling to check it, the channels
will be already released at the end of s3c64xx_spi_transfer_one so the
callback function will return always "false". So, they can't be unmapped
from __spi_unmap_msg call. To fix this, we need to add
unprepare_transfer_hardware callback and move the dma_release_channel
from s3c64xx_spi_transfer_one to there.
Fixes: f52b03c70744 ("spi: s3c64xx: requests spi-dma channel only during data transfer")
Signed-off-by: Chanho Park <chanho61.park@samsung.com>
Link: https://lore.kernel.org/r/20220627013845.138350-1-chanho61.park@samsung.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions