Re: [PATCH v5 03/16] spi: dw: Locally wait for the DMA transactions completion

On Fri, May 29, 2020 at 12:26:10PM +0300, Andy Shevchenko wrote: > On Fri, May 29, 2020 at 11:12:04AM +0300, Serge Semin wrote: > > On Fri, May 29, 2020 at 10:55:32AM +0300, Andy Shevchenko wrote: > > > On Fri, May 29, 2020 at 7:02 AM Serge Semin > > > wrote: > > > > > > > > Even if DMA transactio

Re: [PATCH v5 03/16] spi: dw: Locally wait for the DMA transactions completion

On Fri, May 29, 2020 at 11:12:04AM +0300, Serge Semin wrote: > On Fri, May 29, 2020 at 10:55:32AM +0300, Andy Shevchenko wrote: > > On Fri, May 29, 2020 at 7:02 AM Serge Semin > > wrote: > > > > > > Even if DMA transactions are finished it doesn't mean that the SPI > > > transfers are also complet

Re: [PATCH v5 03/16] spi: dw: Locally wait for the DMA transactions completion

On Fri, May 29, 2020 at 10:55:32AM +0300, Andy Shevchenko wrote: > On Fri, May 29, 2020 at 7:02 AM Serge Semin > wrote: > > > > Even if DMA transactions are finished it doesn't mean that the SPI > > transfers are also completed. It's specifically concerns the Tx-only > > SPI transfers, since there

Re: [PATCH v5 03/16] spi: dw: Locally wait for the DMA transactions completion

On Fri, May 29, 2020 at 7:02 AM Serge Semin wrote: > > Even if DMA transactions are finished it doesn't mean that the SPI > transfers are also completed. It's specifically concerns the Tx-only > SPI transfers, since there might be data left in the SPI Tx FIFO after > the DMA engine notifies that t

[PATCH v5 03/16] spi: dw: Locally wait for the DMA transactions completion

Even if DMA transactions are finished it doesn't mean that the SPI transfers are also completed. It's specifically concerns the Tx-only SPI transfers, since there might be data left in the SPI Tx FIFO after the DMA engine notifies that the Tx DMA procedure is done. In order to completely fix the pr