From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752332Ab3AWVhk (ORCPT ); Wed, 23 Jan 2013 16:37:40 -0500 Received: from mail-ie0-f173.google.com ([209.85.223.173]:39223 "EHLO mail-ie0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752169Ab3AWVhb (ORCPT ); Wed, 23 Jan 2013 16:37:31 -0500 Date: Wed, 23 Jan 2013 16:37:36 -0500 From: Matt Porter To: Mark Brown Cc: Sekhar Nori , Linux DaVinci Kernel List , Linux OMAP List , Russell King , Benoit Cousson , Arnd Bergmann , Linux Documentation List , Tony Lindgren , Devicetree Discuss , Linux MMC List , Linux Kernel Mailing List , Rob Herring , Grant Likely , Vinod Koul , Rob Landley , Dan Williams , Linux SPI Devel List , Chris Ball , Linux ARM Kernel List Subject: Re: [PATCH v5 00/14] DMA Engine support for AM33XX Message-ID: <20130123213736.GC5256@beef> References: <1358281974-8411-1-git-send-email-mporter@ti.com> <50FEB6B2.5020303@ti.com> <20130123022133.GA5727@opensource.wolfsonmicro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130123022133.GA5727@opensource.wolfsonmicro.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 23, 2013 at 10:21:42AM +0800, Mark Brown wrote: > On Tue, Jan 22, 2013 at 09:26:34PM +0530, Sekhar Nori wrote: > > On 1/16/2013 2:02 AM, Matt Porter wrote: > > > > This series adds DMA Engine support for AM33xx, which uses > > > an EDMA DMAC. The EDMA DMAC has been previously supported by only > > > a private API implementation (much like the situation with OMAP > > > DMA) found on the DaVinci family of SoCs. > > > Will you take this series through the OMAP tree? Only 1/14 touches > > mach-davinci and I am mostly okay with it except some changes I just > > requested Matt to make in another thread. > > Is this series somewhere near actually getting merged then? It seemed > like there was lots of stuff going on. The issues raised by Sekhar and Santosh were reasonably minor and will be addressed. My major concern is that the dependency on some api to fetch dmaengine driver SG limitations is not resolved. That's being discussed in https://lkml.org/lkml/2013/1/10/432 If I don't get confirmation from Vinod soon, I'll just take a stab at implementing the callbacks he mentioned in that thread. Static per-channel caps don't provide the information needed by a client driver the uses the EDMA DMAC. Alternatively, we can go back to the hack that looks at the edma phandle and hardcodes the mmc SG limits to magic values, but that's just plain ugly. I could live with it temporarily if we can't get the dmaengine api resolved until 3.10...dunno if others can though. ;) -Matt