Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757404AbYA3HaX (ORCPT ); Wed, 30 Jan 2008 02:30:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753601AbYA3HaK (ORCPT ); Wed, 30 Jan 2008 02:30:10 -0500 Received: from smtp116.sbc.mail.sp1.yahoo.com ([69.147.64.89]:47487 "HELO smtp116.sbc.mail.sp1.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751764AbYA3HaI (ORCPT ); Wed, 30 Jan 2008 02:30:08 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=tjpMDSbJpypCpzqy4tNZaK0sY/Pxbq/sXB//fjblxRbrrf4EJGuBaDbj1SorBrq/XoKc48JXZ6egEXJyDFXth8oozQ5GXmNbxjie39oBhACuMB/kznGDy4mcq5e8bNEE4NgMHd37KmmQFRAhSaT/MvbHOpYAT6pZ9JZ/EWv0Z8c= ; X-YMail-OSG: 6ahvZZsVM1me2SS6JmGZQ7nqWmA8inzLqB2p4aDETlr2eyT9C1BZTjI.xpnC4AJplLwri9gBtA-- X-Yahoo-Newman-Property: ymail-3 From: David Brownell To: Haavard Skinnemoen Subject: Re: [RFC v2 0/5] dmaengine: Slave DMA interface and example users Date: Tue, 29 Jan 2008 22:56:14 -0800 User-Agent: KMail/1.9.6 Cc: Dan Williams , linux-kernel@vger.kernel.org, Shannon Nelson , kernel@avr32linux.org, "Francis Moreau" , "Paul Mundt" , "Vladimir A. Barinov" , Pierre Ossman References: <1201630213-31900-1-git-send-email-hskinnemoen@atmel.com> <20080129215453.1e3758ab@siona> In-Reply-To: <20080129215453.1e3758ab@siona> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801292256.14553.david-b@pacbell.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 868 Lines: 24 On Tuesday 29 January 2008, Haavard Skinnemoen wrote: > > Btw, there's one issue I forgot to mention: I believe the DMA Engine > framework is currently misusing the DMA mapping API, and this patchset > makes things worse. > > Currently, the async_tx bits of the API do the required calls to > dma_map_single() and/or dma_map_page(), but they rely on the driver to > do the unmapping. This is problematic ... > > How do we solve this? How about: for peripheral DMA, don't let the engine see anything except dma_addr_t values. The engine needs to be able to dma_alloc_coherent() memory too, which is pre-mapped. - Dave -- 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/