Received: by 10.192.165.148 with SMTP id m20csp204307imm; Tue, 1 May 2018 21:28:11 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoKxQm6UAVvBunoMj5FpTAk0qRLYL5LAoqDDdzrb3e8jzvmyQh/8yKaRDZt/f5H0NwO6W3u X-Received: by 2002:a63:7413:: with SMTP id p19-v6mr14782167pgc.230.1525235291564; Tue, 01 May 2018 21:28:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525235291; cv=none; d=google.com; s=arc-20160816; b=Y+4ZH3c/eI+OVCMGy2HJg1vSJAumtXU6FXUjOhMmYkvn9TGAFMh8yDc+iSi2sgiPaJ 60ExmKnos8MGu3rvEXfzKfe0SGHAJBEipVCegj2pdyqoOm4laPItI/AIPLpMYoDJ3L3X ig3J2tjelE5vHfQbf8wE9hWVCFPF6hUP+MD7XjHTn7Odb7uG7CUSC+S34ws8GhRdpn2Q C/2dPEmKfI1UfB6MhHELP5zC0SOs1fwuUaOXqYIEIYUwTdzywzLjMhN5dHpLVEk0vUbj JKMIUkLK++7nhp3aqbMWYbznfaKXGaC9ragNu6uweucfGliZSJlZBrpwz7cdOPo3P3QC 6GYw== 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:arc-authentication-results; bh=a33ICMCwPu0tOYajtevpO3GVRibmfNjYqjv7B3nNEdg=; b=woTH1+QxxoF4r2w27EQUAF56nNjwpc637vDB+GwnkMAGugPfbdiZJ4USZ7K4SYaUbF b3Sj4a7DoMqnnlfOunlOP6QhYAx/DTSralMkVeChK4GII/OkDGqE4OgU/4Qu3hvt84F5 bIjyJTKKJcPj7iUGgDrumjxGdal2KBZJr+HBWD2y6c5CiTN99QoXqaa0c90qcfB5oYSQ aTt/tVCUhKRKMx4rM81mmjv3BlLNXpwr/M6Hop8BMv8pFNQ+mCdziBC2JIp4tebNnUKP XEIyWKR5O/6kKafHMn7t60CD9M4XRSdS53iup+CNkhMRsgartZ2YVFMhPIJkvM9V+0oe mCwA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h65-v6si694185pgc.357.2018.05.01.21.27.57; Tue, 01 May 2018 21:28:11 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750918AbeEBE1q (ORCPT + 99 others); Wed, 2 May 2018 00:27:46 -0400 Received: from mga02.intel.com ([134.134.136.20]:16332 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750849AbeEBE1p (ORCPT ); Wed, 2 May 2018 00:27:45 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 May 2018 21:27:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,353,1520924400"; d="scan'208";a="36163167" Received: from vkoul-udesk7.iind.intel.com (HELO localhost) ([10.223.84.143]) by fmsmga007.fm.intel.com with ESMTP; 01 May 2018 21:27:42 -0700 Date: Wed, 2 May 2018 10:02:30 +0530 From: Vinod Koul To: Frank Mori Hess Cc: Vinod Koul , dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org, Dan Williams , r.baldyga@hackerion.com Subject: Re: [PATCH] Revert "dmaengine: pl330: add DMA_PAUSE feature" Message-ID: <20180502043230.GQ6014@localhost> References: <2484918.HKVQc3yJkt@bear> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2484918.HKVQc3yJkt@bear> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Apr 28, 2018 at 05:50:58PM -0400, Frank Mori Hess wrote: > This reverts commit 88987d2c7534a0269f567fb101e6d71a08f0f01d. > > The pl330.c pause implementation violates the dmaengine requirement > for no data loss, since it relies on the DMAKILL > instruction. However, DMAKILL discards in-flight data from the > dma controller's fifo. This is documented in the dma-330 manual > and I have observed it with hardware doing device-to-memory burst > transfers. The discarded data may or may not show up in the > residue count, depending on timing (resulting in data corruption > effectively). I am dropping the orignal patch for queue, so no need for revert patch. -- ~Vinod