Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754987AbaA1LSL (ORCPT ); Tue, 28 Jan 2014 06:18:11 -0500 Received: from gw-1.arm.linux.org.uk ([78.32.30.217]:50705 "EHLO pandora.arm.linux.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753845AbaA1LSK (ORCPT ); Tue, 28 Jan 2014 06:18:10 -0500 Date: Tue, 28 Jan 2014 11:17:57 +0000 From: Russell King - ARM Linux To: Arnd Bergmann Cc: Lars-Peter Clausen , devicetree@vger.kernel.org, Vinod Koul , 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 Message-ID: <20140128111756.GE15937@n2100.arm.linux.org.uk> References: <1390890471-14882-1-git-send-email-agross@codeaurora.org> <1390890471-14882-3-git-send-email-agross@codeaurora.org> <52E772DF.6000604@metafoo.de> <4697306.PPWWh8UGTE@wuerfel> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4697306.PPWWh8UGTE@wuerfel> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.) Not doing this implies that if you have a half-duplex device, you have to repeatedly issue a dmaengine_slave_config() call, a prepare call, and a submit call to the DMA engine code for every segment you want to transfer. We don't need that kind of DMA engine specific behaviour in DMA engine users. -- FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad. Estimate before purchase was "up to 13.2Mbit". -- 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/