From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759934Ab1JGL1G (ORCPT ); Fri, 7 Oct 2011 07:27:06 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:64524 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759832Ab1JGL1E (ORCPT ); Fri, 7 Oct 2011 07:27:04 -0400 MIME-Version: 1.0 In-Reply-To: <1317966346.1573.2252.camel@vkoul-udesk3> References: <1317191992-3635-1-git-send-email-jaswinder.singh@linaro.org> <1317200618.1573.1765.camel@vkoul-udesk3> <1317295068.1573.1780.camel@vkoul-udesk3> <20111003161349.GB28287@flint.arm.linux.org.uk> <1317966346.1573.2252.camel@vkoul-udesk3> Date: Fri, 7 Oct 2011 16:57:03 +0530 Message-ID: Subject: Re: [PATCHv4] DMAEngine: Define interleaved transfer request api From: Jassi Brar To: Vinod Koul Cc: "Williams, Dan J" , Russell King , Barry Song <21cnbao@gmail.com>, linux-kernel@vger.kernel.org, DL-SHA-WorkGroupLinux , Dave Jiang Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7 October 2011 11:15, Vinod Koul wrote: > Thru this patch Jassi gave a very good try at merging DMA_SLAVE and > memcpy, but more we debate this, I am still not convinced about merging > memcpy and DMA_SLAVE yet. > Nobody is merging memcpy and DMA_SLAVE right away. The api's primary purpose is to support interleave transfers. Possibility to merge other prepares into this is a side-effect. > I would still argue that if we split this on same lines as current > mechanism, we have clean way to convey all details for both cases. > Do you mean to have separate interleaved transfer apis for Slave and Mem->Mem ? Please clarify.