drivers: serial: stm32wba: Suspension required before stop in DMA Tx abort
In a previous change, STM32U5 GPDMA specific behavior was set into a specific configuration applying only to few devices impacted by a specific silicon erratum. As part of this change, dma suspension before dma stop was set to apply to the specific erratum workaround. It appears, this was wrong and dma suspension before dma stop should be done on all devices compatible with stm32u5 dma. This fix re-instantiate the correct behavior. Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
This commit is contained in:
parent
ad1594ee75
commit
d2ea9e4806
1 changed files with 1 additions and 1 deletions
|
@ -1633,7 +1633,7 @@ static int uart_stm32_async_tx_abort(const struct device *dev)
|
|||
data->dma_tx.counter = tx_buffer_length - stat.pending_length;
|
||||
}
|
||||
|
||||
#ifdef CONFIG_UART_STM32U5_ERRATA_DMAT
|
||||
#if DT_HAS_COMPAT_STATUS_OKAY(st_stm32u5_dma)
|
||||
dma_suspend(data->dma_tx.dma_dev, data->dma_tx.dma_channel);
|
||||
#endif
|
||||
dma_stop(data->dma_tx.dma_dev, data->dma_tx.dma_channel);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue