Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755315Ab2BAI3I (ORCPT ); Wed, 1 Feb 2012 03:29:08 -0500 Received: from mga11.intel.com ([192.55.52.93]:19078 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753949Ab2BAI3G (ORCPT ); Wed, 1 Feb 2012 03:29:06 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="118996499" Subject: Re: [PATCH v2 0/2] Add Qualcomm MSM ADM DMAEngine driver From: Vinod Koul To: Ravi Kumar V Cc: linux-arch@vger.kernel.org, tsoni@codeaurora.org, linux@arm.linux.org.uk, arnd@arndb.de, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, bryanh@codeaurora.org, johlstei@codeaurora.org, Daniel Walker , dan.j.williams@intel.com, davidb@codeaurora.org, linux-arm-kernel@lists.infradead.org In-Reply-To: <4F28D8A2.9050605@codeaurora.org> References: <1325854052-21402-1-git-send-email-kumarrav@codeaurora.org> <1326807902.1540.116.camel@vkoul-udesk3> <4F195E4C.6080805@codeaurora.org> <1327066287.517.4.camel@vkoul-udesk3> <4F1D4052.3070701@codeaurora.org> <1327326713.517.32.camel@vkoul-udesk3> <4F1FFF7E.3000802@codeaurora.org> <1327911315.1527.8.camel@vkoul-udesk3> <4F278341.4020600@codeaurora.org> <1327990151.1527.80.camel@vkoul-udesk3> <4F28D8A2.9050605@codeaurora.org> Content-Type: text/plain; charset="UTF-8" Date: Wed, 01 Feb 2012 13:59:58 +0530 Message-ID: <1328084998.1610.11.camel@vkoul-udesk3> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1230 Lines: 34 On Wed, 2012-02-01 at 11:46 +0530, Ravi Kumar V wrote: > On 1/31/2012 11:39 AM, Vinod Koul wrote: > > On Tue, 2012-01-31 at 11:29 +0530, Ravi Kumar V wrote: > >>> [1]: https://lkml.org/lkml/2011/10/24/275 > >>> [2]: https://lkml.org/lkml/2012/1/26/405 > >>> > >> > >> Yes if we follow the above RFC and add extra context parameter also > >> in > >> device_prep_dma_sg()& device_prep_interleaved_dma() then it supports > >> our hardware and our work will be completed. > >> > >> can we follow above RFC and implement our driver. > >> Is above RFC finalized and included in mainline? > > Alexandre will post an updated one soon, but the idea is same > > > > Can we add extra parameter context to device_prep_dma_sg() & > device_prep_interleaved_dma() API's and implement our driver. So what one are you going to use... >From the description sounds like you need interleaved API but with changes to make it interleaved in both src and dtsn, right? Then why prep_dma_sg? -- ~Vinod -- 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/