Received-SPF: pass (google.com: domain of linux-kernel+bounces-122514-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: Vinod Koul <vkoul@kernel.org>
To: ldewangan@nvidia.com, jonathanh@nvidia.com, thierry.reding@gmail.com, 
 dmaengine@vger.kernel.org, linux-tegra@vger.kernel.org, 
 linux-kernel@vger.kernel.org, Akhil R <akhilrajeev@nvidia.com>
In-Reply-To: <20240315124411.17582-1-akhilrajeev@nvidia.com>
References: <20240315124411.17582-1-akhilrajeev@nvidia.com>
Subject: Re: [PATCH v2 RESEND] dmaengine: tegra186: Fix residual
 calculation
Message-Id: <171161158127.113367.3353184486729352623.b4-ty@kernel.org>
Date: Thu, 28 Mar 2024 13:09:41 +0530
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit


On Fri, 15 Mar 2024 18:14:11 +0530, Akhil R wrote:
> The existing residual calculation returns an incorrect value when
> bytes_xfer == bytes_req. This scenario occurs particularly with drivers
> like UART where DMA is scheduled for maximum number of bytes and is
> terminated when the bytes inflow stops. At higher baud rates, it could
> request the tx_status while there is no bytes left to transfer. This will
> lead to incorrect residual being set. Hence return residual as '0' when
> bytes transferred equals to the bytes requested.
> 
> [...]

Applied, thanks!

[1/1] dmaengine: tegra186: Fix residual calculation
      commit: 30f0ced9971b2d8c8c24ae75786f9079489a012d

Best regards,
-- 
~Vinod