Date: Fri, 25 Nov 2016 11:06:04 +0530
From: Vinod Koul <vinod.koul@intel.com>
To: Nandor Han <nandor.han@ge.com>
Cc: Dan Williams <dan.j.williams@intel.com>, dmaengine@vger.kernel.org,
        linux-kernel@vger.kernel.org,
        Peter Senna Tschudin <peter.senna@collabora.com>,
        Marek Vasut <marex@denx.de>
Subject: Re: [PATCH 1/1] dmaengine: imx-sdma - correct the dma transfer
 residue calculation
Message-ID: <20161125053604.GD2698@localhost>
References: <cover.1476172445.git.nandor.han@ge.com>
 <0ee9c1d80055ce97cf6cdcc4aa2ce38b293547b7.1476172445.git.nandor.han@ge.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0ee9c1d80055ce97cf6cdcc4aa2ce38b293547b7.1476172445.git.nandor.han@ge.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 872
Lines: 20

On Tue, Oct 11, 2016 at 02:13:41PM +0300, Nandor Han wrote:
> The residue calculation was taking in consideration that dma
> transaction status will be always retrieved in the dma callback
> used to inform that dma transfer is complete. However this is not
> the case for all subsystems that use dma. Some subsystems use a
> timer to check the dma status periodically.
> 
> Therefore the calculation was updated and residue is calculated
> accordingly by a) update the residue calculation taking in
> consideration the last used buffer index by using *buf_ptail* variable
> and b) chn_real_count (number of bytes transferred) is initialized to
> zero, when dma channel is created, to avoid using an uninitialized
> value in residue calculation when dma status is checked without
> waiting dma complete event.

Looks to be missed earier, so applying now

Thanks
-- 
~Vinod