Subject: Re: DMA mapping API for non-system memory pools
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Russell King <rmk@arm.linux.org.uk>,
       Linux Kernel list <linux-kernel@vger.kernel.org>
In-Reply-To: <4479FB80-8703-4BCA-925E-DA25B65EE916@kernel.crashing.org>
References: <4479FB80-8703-4BCA-925E-DA25B65EE916@kernel.crashing.org>
Content-Type: text/plain
Date: Fri, 09 Feb 2007 18:53:29 -0500
Message-Id: <1171065209.3627.38.camel@mulgrave.il.steeleye.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 782
Lines: 20

On Fri, 2007-02-09 at 17:33 -0600, Kumar Gala wrote:
> ideally all this would be handled via the dma mapping API, the  
> question is how to convey to the API to use the IO memory vs the  
> system memory?  Should we look at adding a new GFP_IOMEM flag or do  
> something based on struct device?
> 
> Any ideas on direction (or if this is a solved problem elsewhere)  
> would be appreciated.

Doesn't the dma_declare_coherent_memory() API work for this case?  it
was designed for the ARM SoC (and the voyager weird SCSI card).

James


-
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/