From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0CAA0C3A59E for ; Wed, 4 Sep 2019 05:57:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D359423404 for ; Wed, 4 Sep 2019 05:57:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567576624; bh=vHzjJabvLNobLJbAo+1Q1mNco/nbArtdiV86fXt8HaE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=ld3vT+HQ9sN/qZ4AMXcA0Zq+KmUvXj/8Ol4JX05hVs/szz3YyaGhWu5saWmkfXj2O 60xCRcdPs8J5/byZLe8/tr4NQHByYBqDClZp5z8+lVwUjCJusRY8wzT004o/1tFsHn utB8dboJeRvuEOGnozzIYwz5m1fxZbFAY/C4nBTY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725947AbfIDF5E (ORCPT ); Wed, 4 Sep 2019 01:57:04 -0400 Received: from mail.kernel.org ([198.145.29.99]:52072 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725774AbfIDF5E (ORCPT ); Wed, 4 Sep 2019 01:57:04 -0400 Received: from localhost (unknown [122.182.201.156]) (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 BD2FB23400; Wed, 4 Sep 2019 05:57:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567576623; bh=vHzjJabvLNobLJbAo+1Q1mNco/nbArtdiV86fXt8HaE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=n97BL6VG/PiUpyRJrrHJrNi8SJ1v7450/uyMdXvkaqFJ2S47p6welwcU+R6u8OViV 1bMaGux6SPNAokx6QEGp3U4w4V6fp22ozmM2ebl7sUKNsC4U3EBLwR+qmsT+djwXWg 9nBzebhPlFtAzd18kU+v6fZ2bhOJDKdqV+FZgFmA= Date: Wed, 4 Sep 2019 11:25:55 +0530 From: Vinod Koul To: Baolin Wang Cc: orsonzhai@gmail.com, zhang.lyra@gmail.com, dan.j.williams@intel.com, linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org, eric.long@unisoc.com Subject: Re: [PATCH] dmaengine: sprd: Fix the DMA link-list configuration Message-ID: <20190904055555.GD2672@vkoul-mobl> References: <77868edb7aff9d5cb12ac3af8827ef2e244441a6.1567150471.git.baolin.wang@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <77868edb7aff9d5cb12ac3af8827ef2e244441a6.1567150471.git.baolin.wang@linaro.org> User-Agent: Mutt/1.12.0 (2019-05-25) Sender: dmaengine-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: dmaengine@vger.kernel.org On 30-08-19, 15:37, Baolin Wang wrote: > For the Spreadtrum DMA link-list mode, when the DMA engine got a slave > hardware request, which will trigger the DMA engine to load the DMA > configuration from the link-list memory automatically. But before the > slave hardware request, the slave will get an incorrect residue due > to the first node used to trigger the link-list was configured as the > last source address and destination address. > > Thus we should make sure the first node was configured the start source > address and destination address, which can fix this issue. Applied, thanks -- ~Vinod