Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp3081541pxb; Mon, 9 Nov 2020 01:52:58 -0800 (PST) X-Google-Smtp-Source: ABdhPJyI1ZzzNZyn3d02C3KdSB30az5rCU2nXlE3vNbsy4shFarIHGwqj3/N5JufCQRApPGafTAE X-Received: by 2002:a17:906:f18f:: with SMTP id gs15mr14579056ejb.474.1604915578687; Mon, 09 Nov 2020 01:52:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1604915578; cv=none; d=google.com; s=arc-20160816; b=I8Hc73roqMTbZfG4Efaak0ZRW7xkPyPFQazK0zyfdzpN6HfY9RYWNLOSHUeoFTEVoR DXYtBynU3IJnumZ+wPQ+IA3Ylnev5NSDBTJUB/qk4DSljTyaFFt//ER/EpXu9SA2yCdf m2i3uU3LhwVZ+yGXANaZKL0uXXEMC+4WARsynDtnV9M88OhLGBRTIVJnMyBcK3nlWwNl OGrm38KF1NIPBhoE4ZJx0x+FET9kQZQvJWgipRBvygEQpP5wGLOQBxHcGuzLdEWfUFOQ cc4nzH4nVpxXXsrJQSKVDQZV7++ltAMmPAJEH6e9oWUg6KoL/3r+2hVRqMaK+4zsE8iD jyyQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=vZuIXlIVnCElk1sIyWVLoF29EoiNElYGkX2rLXwoVu4=; b=1AVJ0+OJ070BKrCX5BhkTNQL4RMOOtTqNGxP0M8ZYs8YwBEdF2CI2wQTS709sVvELF 8i3POFX5y45R8nmri/28sKsfgw3355TZ5a3wSLDQ7WGZTVo7aFj6ASKqE/vnDAZBgCnr OjMt7Bd4UWXfOwpKgW7fhxXEGv56ueVB5FmTORWHy6EEKdJ2p+OD4mcj7XbTLGoiswoO i/R03rztWKNha7fzAsqHVuaZ/387a63QOpirOkg5vCj4xp20OpwK0OgMin0ipzTNLjlg yvolQ00on2C64I7mNtujAfwewT71DonubPu9dfiT4FKlGMNfOZ0Sz2dm+nZvPzHitqkf vOhQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=XSQ6GxkY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x72si6096442ede.132.2020.11.09.01.52.35; Mon, 09 Nov 2020 01:52:58 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=XSQ6GxkY; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727906AbgKIJvV (ORCPT + 99 others); Mon, 9 Nov 2020 04:51:21 -0500 Received: from mail.kernel.org ([198.145.29.99]:60674 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726482AbgKIJvU (ORCPT ); Mon, 9 Nov 2020 04:51:20 -0500 Received: from localhost (unknown [122.171.147.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 09E3C2067B; Mon, 9 Nov 2020 09:51:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604915480; bh=J8ZtzV9PxdarTa9B5TSlOWHmWZ3DYcHZro6XdfuNMJg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=XSQ6GxkYgGbtHuTMgdVMGjgyQKFh8eVQKB+YqoxbdnukYjNYSBEB89ng4O77vuMFD dEs02/3wJ2IcImaB/cT4v99ehGdtmxsHk7LvWoyBm85fAyuC5J4BkGqd0aW5VfxCWl CP5a6A0geGYDBoJI9jataDrWX+axYbHiKxAOR5dY= Date: Mon, 9 Nov 2020 15:21:15 +0530 From: Vinod Koul To: Sia Jee Heng Cc: Eugeniy.Paltsev@synopsys.com, andriy.shevchenko@linux.intel.com, dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 09/15] dmaengine: dw-axi-dmac: Support burst residue granularity Message-ID: <20201109095115.GD3171@vkoul-mobl> References: <20201027063858.4877-1-jee.heng.sia@intel.com> <20201027063858.4877-10-jee.heng.sia@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201027063858.4877-10-jee.heng.sia@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 27-10-20, 14:38, Sia Jee Heng wrote: > Add support for DMA_RESIDUE_GRANULARITY_BURST so that AxiDMA can report > DMA residue. > > Existing AxiDMA driver only support data transfer between > memory to memory operation, therefore reporting DMA residue > to the DMA clients is not supported. > > Reporting DMA residue to the DMA clients is important as DMA clients > shall invoke dmaengine_tx_status() to understand the number of bytes > been transferred so that the buffer pointer can be updated accordingly. > > Reviewed-by: Andy Shevchenko > Signed-off-by: Sia Jee Heng > --- > .../dma/dw-axi-dmac/dw-axi-dmac-platform.c | 44 ++++++++++++++++--- > drivers/dma/dw-axi-dmac/dw-axi-dmac.h | 2 + > 2 files changed, 39 insertions(+), 7 deletions(-) > > diff --git a/drivers/dma/dw-axi-dmac/dw-axi-dmac-platform.c b/drivers/dma/dw-axi-dmac/dw-axi-dmac-platform.c > index 011cf7134f25..cd99557a716c 100644 > --- a/drivers/dma/dw-axi-dmac/dw-axi-dmac-platform.c > +++ b/drivers/dma/dw-axi-dmac/dw-axi-dmac-platform.c > @@ -265,14 +265,36 @@ dma_chan_tx_status(struct dma_chan *dchan, dma_cookie_t cookie, > struct dma_tx_state *txstate) > { > struct axi_dma_chan *chan = dchan_to_axi_dma_chan(dchan); > - enum dma_status ret; > + struct virt_dma_desc *vdesc; > + enum dma_status status; > + u32 completed_length; > + unsigned long flags; > + u32 completed_blocks; > + size_t bytes = 0; > + u32 length; > + u32 len; > > - ret = dma_cookie_status(dchan, cookie, txstate); > + status = dma_cookie_status(dchan, cookie, txstate); txstate can be null, so please check that as well in the below condition and return if that is the case -- ~Vinod