Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755157AbaA1MFs (ORCPT ); Tue, 28 Jan 2014 07:05:48 -0500 Received: from moutng.kundenserver.de ([212.227.17.8]:56590 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753894AbaA1MFq (ORCPT ); Tue, 28 Jan 2014 07:05:46 -0500 From: Arnd Bergmann To: Vinod Koul Cc: Russell King - ARM Linux , Lars-Peter Clausen , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, Andy Gross , dmaengine@vger.kernel.org, Dan Williams , linux-arm-kernel@lists.infradead.org Subject: Re: [Patch v3 2/2] dmaengine: qcom_bam_dma: Add device tree binding Date: Tue, 28 Jan 2014 13:05:10 +0100 Message-ID: <4916428.f0GtxdkWKj@wuerfel> User-Agent: KMail/4.11 rc1 (Linux/3.10.0-5-generic; KDE/4.11.2; x86_64; ; ) In-Reply-To: <20140128113242.GJ10628@intel.com> References: <1390890471-14882-1-git-send-email-agross@codeaurora.org> <20140128111756.GE15937@n2100.arm.linux.org.uk> <20140128113242.GJ10628@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V02:K0:ZHTIb8taVXlAOOUSIM26rRTQ5h4ixSiTlWEuL1CS7Zg kEGR5YJz/HscHeeQE15UVB6ucxId3ZtlRgZlbbCt6mYQ5d2AvH 8oZ2CUW5aK4NqTApVVpn95sHK5dXCdvZFNY01adQC1YYX4Drzg 2jCmqc9jX5td6qog/HErl9pBGdShGFlAQOkgyLsXluUUCWj8iP ntGtm8H+htgiAYU5+4KWzZMKt+Lt56tQXSEKIb1LjBjlrjLyUX 7K6/esMA1NfW1J8aUCIEsPLuUqX6jqOkVKsLJgSeVdUb5LmnPG EAltKdqwJ/cTK9Ut9Ebvr3x+x15AHdAB+4pxvxwvUMOlv4ktN/ 6fwaNKSToPWBjf+HEhGk= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 28 January 2014 17:02:42 Vinod Koul wrote: > On Tue, Jan 28, 2014 at 11:17:57AM +0000, Russell King - ARM Linux wrote: > > On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote: > > > On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote: > > > > Why does the direction needs to be specified in specifier? I see two > > > > options, either the direction per is fixed in hardware. In that case the DMA > > > > controller node should describe which channel is which direction. Or the > > > > direction is not fixed in hardware and can be changed at runtime in which > > > > case it should be set on a per descriptor basis. > > > > > > Normally the direction is implied by dmaengine_slave_config(). > > > > No. The direction argument in there is deprecated - we've been talking > > about removing it for some time. > > > > DMA engine drivers should store all parameters of the configuration, and > > then select the appropriate ones when preparing a transfer (which itself > > involves a direction.) > > Right all the prep_ calls for slave cases have explcit direction argument so > sending it using slave config makes no sense. So will remove it after the merge > window closes and fix Ok, thanks for clearing up my mistake. However, the argument remains: the direction doesn't need to be in the DT DMA descriptor since it gets set by software anyway. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/