Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp1096459imm; Tue, 3 Jul 2018 05:34:05 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIwFdOFAMxPDVy+mIoD2M73CGKZ5/R4qtP7yZeUTk2zqgyka4o9U86JnIn0XnLxueg94mRu X-Received: by 2002:a17:902:543:: with SMTP id 61-v6mr30046124plf.47.1530621245048; Tue, 03 Jul 2018 05:34:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530621245; cv=none; d=google.com; s=arc-20160816; b=db8HWQuiKb50SExk2yDpfxmZTy7KpngTPt/05Ds+OwmboSwlR2DrwxEbdeW4chYI5B RNynH4gf1wGiT9V5G7KtGBpT6GYcDCnluhye4PogTbwdVTtYl8JiKdWop5PvlUNWASuO 1Kbbz8jXJTioPBUuof/zHbKbWPN5WjgfQR6Wcr9B88WLzNZBvNhu5cnzNWMY39ZYCcEu YJ421gtsyXbGqd25UOxc9+CPAY/DQWtL6lOUZZTeAi2w2y0f5spt6Zq84U4WwBW1bsJs 0doMZhOege8XzEgo2Z9VPDAskJ4R2UP3WGml824drIHcPtXOE+zoHn+4wnTSUPTxlKV9 CzvQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:references:in-reply-to :message-id:date:subject:cc:to:from:arc-authentication-results; bh=Epn573GskJFJvAe4jqYI3koEfREZS0jGyFdeVeplzcQ=; b=ytH9g91YDwZSDR/umcAcW/icu79MadN6f+6NsTJEhyhCcSRIx6GjhX+EzcdVymE9M7 +cp+9cm7MtE+3olgRrU/hIDgskBg3PTeCWufHSBx/qIuJm7xOIWpqpxDIee99xXv1+Zm LTJEmGScfMN8rcHr7rO8YbRZssC48P/8aUoQ+nHQ2aevUWffMWP8r2/CXUHOM0tFhKs5 +OV9ae7UeWPPaBSOvjYP5cUNikN8lq6vTYE0PN/tMklOqN1cekoVm6bSEOCeZ6kit01J d1PZlQ2nES2Z3EiIRxZL9k9HClONjuVuIINDXWT0pU1UHXF1Ya3XJ8eflp0NPWdFL0t4 TCqQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@crapouillou.net header.s=mail header.b=mxT5pLdE; 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=crapouillou.net Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i4-v6si971548pgl.435.2018.07.03.05.33.50; Tue, 03 Jul 2018 05:34:05 -0700 (PDT) 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=@crapouillou.net header.s=mail header.b=mxT5pLdE; 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=crapouillou.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932318AbeGCMcq (ORCPT + 99 others); Tue, 3 Jul 2018 08:32:46 -0400 Received: from outils.crapouillou.net ([89.234.176.41]:47020 "EHLO crapouillou.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932127AbeGCMcl (ORCPT ); Tue, 3 Jul 2018 08:32:41 -0400 From: Paul Cercueil To: Vinod Koul , Rob Herring , Mark Rutland , Ralf Baechle , Paul Burton , James Hogan , Zubair Lutfullah Kakakhel Cc: Mathieu Malaterre , Daniel Silsby , dmaengine@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mips@linux-mips.org Subject: [PATCH 10/14] dmaengine: dma-jz4780: Set DTCn register explicitly Date: Tue, 3 Jul 2018 14:32:10 +0200 Message-Id: <20180703123214.23090-11-paul@crapouillou.net> In-Reply-To: <20180703123214.23090-1-paul@crapouillou.net> References: <20180703123214.23090-1-paul@crapouillou.net> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=crapouillou.net; s=mail; t=1530621160; bh=Epn573GskJFJvAe4jqYI3koEfREZS0jGyFdeVeplzcQ=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References; b=mxT5pLdE6yGZotowjGmckqXQbgjpmtGDNEhE1iqbkPtHt/zek5a6Iz/HGe7Zs8askoumTgRmxPtwrxVdRHnG7L078bMyxxGXjjh5OKMBJ/F65cw1dttQS7bxccfq64Ju1LB3mM7k/WeZ9Jazsy/KW0wOuqPkgV1XYfsFJ5Qzzdc= Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Daniel Silsby Normally, we wouldn't set the channel transfer count register directly when using descriptor-driven transfers. However, there is no harm in doing so, and it allows jz4780_dma_desc_residue() to report the correct residue of an ongoing transfer, no matter when it is called. Signed-off-by: Daniel Silsby --- drivers/dma/dma-jz4780.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/drivers/dma/dma-jz4780.c b/drivers/dma/dma-jz4780.c index adada2a3a067..64270d53ba57 100644 --- a/drivers/dma/dma-jz4780.c +++ b/drivers/dma/dma-jz4780.c @@ -526,6 +526,15 @@ static void jz4780_dma_begin(struct jz4780_dma_chan *jzchan) jz4780_dma_chn_writel(jzdma, jzchan->id, JZ_DMA_REG_DRT, jzchan->transfer_type); + /* + * Set the transfer count. This is redundant for a descriptor-driven + * transfer. However, there can be a delay between the transfer start + * time and when DTCn reg contains the new transfer count. Setting + * it explicitly ensures residue is computed correctly at all times. + */ + jz4780_dma_chn_writel(jzdma, jzchan->id, JZ_DMA_REG_DTC, + jzchan->desc->desc[jzchan->curr_hwdesc].dtc); + /* Write descriptor address and initiate descriptor fetch. */ desc_phys = jzchan->desc->desc_phys + (jzchan->curr_hwdesc * sizeof(*jzchan->desc->desc)); -- 2.18.0