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: e2c97d200ac3558e6c34258c96a01a0b9472292f
[2/6] dmaengine: dw: Add memory bus width verification
commit: 5bb11aedb5309c232967ce490d7b826536f697c0
[3/6] dmaengine: dw: Simplify prepare CTL_LO methods
commit: d34e8466c63389ef250c380cd615826afb2a049c
[4/6] dmaengine: dw: Define encode_maxburst() above prepare_ctllo() callbacks
commit: 2f87a9671ed532fc088ef0b05e350637afdf001a
[5/6] dmaengine: dw: Simplify max-burst calculation procedure
commit: 17d4353413a4d931e89b2c37106acae4a0972ad8
[6/6] dmaengine: dw: Unify ret-val local variables naming
commit: 3f92ee7c4a4e2319d510eb2ddcfdd3105b235f0e
Best regards,
--
~Vinod
