Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp118129ybc; Mon, 11 Nov 2019 21:40:10 -0800 (PST) X-Google-Smtp-Source: APXvYqzKdA03eXL6MdHaWAmtK+Whw9RVZjpfAK6lkgoroKui5kEKbVf/pvnZ4NNXAtmRPmG0Q0S3 X-Received: by 2002:a17:906:4a0c:: with SMTP id w12mr26566283eju.306.1573537209993; Mon, 11 Nov 2019 21:40:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573537209; cv=none; d=google.com; s=arc-20160816; b=RYbIKX8cZlmyIXQKEofFOokapw94FXGT7kZqQi6/jVEpTr6KzK90fi8YG8hAC5J8zF DrvT7syBb6nFP7sFBtyVchAPP26t/JCmEKZo+OLLw7rU1k1UCFSQdxkZnRl6ssb39j/p 69tYv2AldDKOdYVzQK+hTlhIJl972uFxxW8iSAkbByD7XHxU/vv6Q5s7RqwH6F80GGo1 hnCoYPPGhxwtLZLA8Wrw/31cQ0wfXRa44tlZTlkx3VJXe6xNB4tcRb73ZYSvnzNY8JC7 4cDYq+DgBRM2JeBsALB38ocJ2wZVeYkv7XyuSP4s1sip1SbebeI9IdSq0Fnmr4y5PHM0 o9cg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=RHeVEaOt+8aESaE/o/AGCuKIStQfM8zPchEyiMROxSk=; b=bpNzjc9Snsr++BciljnaaS4sxVDA2VQU39lry94pKHXZw7baflhQyy6u8yhA6kQKqq dlhOgqUP7h3YAIFuIJ4A9d2dfim6DR2UG0d/7UQ2QCUT7h76edwWJL98vyOfSPAdtFCp AFrpZbtPBXARa4qiFn9LM+CWKToR6SOe16ymHhh65DJWgkJ/2WaDBbpdtXX0Uaz20dsv PlP7KUymltt3Hcdc0kOzeftqOipKSs2hsD2uOHomvJVFRxoXMpr4rYcNQKKFCCV+JfUK V4NRxVjzfbcvj7rnLiMP0p/TU9oxUzzgauo3qjvuLmNZ6cpoJLSe2GF4WZtuleT04prj lzkg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="sP/sZWa6"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id f6si11175194ejx.0.2019.11.11.21.39.45; Mon, 11 Nov 2019 21:40:09 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="sP/sZWa6"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S1726983AbfKLFg1 (ORCPT + 99 others); Tue, 12 Nov 2019 00:36:27 -0500 Received: from mail.kernel.org ([198.145.29.99]:33100 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725283AbfKLFg0 (ORCPT ); Tue, 12 Nov 2019 00:36:26 -0500 Received: from localhost (unknown [122.167.70.123]) (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 6960321783; Tue, 12 Nov 2019 05:36:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1573536986; bh=YDjjnafho2uCvMpxMXlnLJhhfTeoSuyoFzfDVXn7/m4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=sP/sZWa6JWAiI7hq87AEWqr9AfSulRdI9YTrCKxSrQ9hoL4y7OXcCBvFDo6lhJO0f FeJ/Vqsm9SzcuKMOUI1LrLDl4Fp3KOIMDqB1bOIZf5z1Xn5+3hQ0ld7AfxnpvhMfIT NS+jfbiH+eK3W0HryxKa7RJk06UWxK51nrET6tF0= Date: Tue, 12 Nov 2019 11:06:21 +0530 From: Vinod Koul To: Peter Ujfalusi Cc: robh+dt@kernel.org, nm@ti.com, ssantosh@kernel.org, dan.j.williams@intel.com, dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, grygorii.strashko@ti.com, lokeshvutla@ti.com, t-kristo@ti.com, tony@atomide.com, j-keerthy@ti.com Subject: Re: [PATCH v4 12/15] dmaengine: ti: New driver for K3 UDMA - split#4: dma_device callbacks 1 Message-ID: <20191112053621.GW952516@vkoul-mobl> References: <20191101084135.14811-1-peter.ujfalusi@ti.com> <20191101084135.14811-13-peter.ujfalusi@ti.com> <20191111060943.GQ952516@vkoul-mobl> <6d73f6e1-6d85-d468-2e69-47d36ed75807@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6d73f6e1-6d85-d468-2e69-47d36ed75807@ti.com> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11-11-19, 12:29, Peter Ujfalusi wrote: > On 11/11/2019 8.09, Vinod Koul wrote: > > On 01-11-19, 10:41, Peter Ujfalusi wrote: > >> +static enum dma_status udma_tx_status(struct dma_chan *chan, > >> + dma_cookie_t cookie, > >> + struct dma_tx_state *txstate) > >> +{ > >> + struct udma_chan *uc = to_udma_chan(chan); > >> + enum dma_status ret; > >> + unsigned long flags; > >> + > >> + spin_lock_irqsave(&uc->vc.lock, flags); > >> + > >> + ret = dma_cookie_status(chan, cookie, txstate); > >> + > >> + if (!udma_is_chan_running(uc)) > >> + ret = DMA_COMPLETE; > > > > so a paused channel will result in dma complete status? > > The channel is still enabled (running), the pause only sets a bit in the > channel's real time control register. Okay and which cases will channel not be running i.e., you return DMA_COMPLETE above? -- ~Vinod