diff options
| author | Bin Liu <[email protected]> | 2024-10-31 12:23:15 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2024-11-05 14:03:53 +0100 |
| commit | bcc7ba668818dcadd2f1db66b39ed860a63ecf97 (patch) | |
| tree | 1c83b55c8de50abd014c5cb7ace5afe189afefbe /tools/perf/scripts/python/check-perf-trace.py | |
| parent | 7dcb7bf4a2baf314edf06752093fc64bda9e517d (diff) | |
serial: 8250: omap: Move pm_runtime_get_sync
Currently in omap_8250_shutdown, the dma->rx_running flag is
set to zero in omap_8250_rx_dma_flush. Next pm_runtime_get_sync
is called, which is a runtime resume call stack which can
re-set the flag. When the call omap_8250_shutdown returns, the
flag is expected to be UN-SET, but this is not the case. This
is causing issues the next time UART is re-opened and
omap_8250_rx_dma is called. Fix by moving pm_runtime_get_sync
before the omap_8250_rx_dma_flush.
cc: [email protected]
Fixes: 0e31c8d173ab ("tty: serial: 8250_omap: add custom DMA-RX callback")
Signed-off-by: Bin Liu <[email protected]>
[Judith: Add commit message]
Signed-off-by: Judith Mendez <[email protected]>
Reviewed-by: Kevin Hilman <[email protected]>
Tested-by: Kevin Hilman <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions