On Fri, 02 Aug 2024 10:50:45 +0300, Serge Semin wrote:
> The main goal of this series is to fix the data disappearance in case of
> the DW UART handled by the DW AHB DMA engine. The problem happens on a
> portion of the data received when the pre-initialized DEV_TO_MEM
> DMA-transfer is paused and then disabled. The data just hangs up in the
> DMA-engine FIFO and isn't flushed out to the memory on the DMA-channel
> suspension (see the second commit log for details). On a way to find the
> denoted problem fix it was discovered that the driver doesn't verify the
> peripheral device address width specified by a client driver, which in its
> turn if unsupported or undefined value passed may cause DMA-transfer being
> misconfigured. It's fixed in the first patch of the series.
>
> [...]
Applied, thanks!
[1/6] dmaengine: dw: Add peripheral bus width verification
commit: b336268dde75cb09bd795cb24893d52152a9191f
[2/6] dmaengine: dw: Add memory bus width verification
commit: d04b21bfa1c50a2ade4816cab6fdc91827b346b1
[3/6] dmaengine: dw: Simplify prepare CTL_LO methods
commit: 1fd6fe89055e6dbb4be8f16b8dcab8602e3603d6
[4/6] dmaengine: dw: Define encode_maxburst() above prepare_ctllo() callbacks
commit: 3acb301d33749a8974e61ecda16a5f5441fc9628
[5/6] dmaengine: dw: Simplify max-burst calculation procedure
commit: d8fa0802f63502c0409d02c6b701d51841a6f1bd
[6/6] dmaengine: dw: Unify ret-val local variables naming
commit: 2ebc36b9581df31eed271e5de61fc8a8b66dbc56
Best regards,
--
Vinod Koul <vkoul@xxxxxxxxxx>
