Re: [PATCH 3/3] dmaengine: at_xdmac: double FIFO flush needed to compute residue

Le 12/05/2016 16:54, Ludovic Desroches a écrit : > Due to the way CUBC register is updated, a double flush is needed to > compute an accurate residue. First flush aim is to get data from the DMA > FIFO and second one ensures that we won't report data which are not in > memory. > > Signed-off-by:

Re: [PATCH 3/3] dmaengine: at_xdmac: double FIFO flush needed to compute residue

Le 12/05/2016 16:54, Ludovic Desroches a écrit : > Due to the way CUBC register is updated, a double flush is needed to > compute an accurate residue. First flush aim is to get data from the DMA > FIFO and second one ensures that we won't report data which are not in > memory. > > Signed-off-by:

[PATCH 3/3] dmaengine: at_xdmac: double FIFO flush needed to compute residue

Due to the way CUBC register is updated, a double flush is needed to compute an accurate residue. First flush aim is to get data from the DMA FIFO and second one ensures that we won't report data which are not in memory. Signed-off-by: Ludovic Desroches Fixes:

[PATCH 3/3] dmaengine: at_xdmac: double FIFO flush needed to compute residue

Due to the way CUBC register is updated, a double flush is needed to compute an accurate residue. First flush aim is to get data from the DMA FIFO and second one ensures that we won't report data which are not in memory. Signed-off-by: Ludovic Desroches Fixes: e1f7c9eee707 ("dmaengine: at_xdmac: