LKML Archive on
help / color / mirror / Atom feed
From: James Bottomley <>
To: Kumar Gala <>
Cc: Russell King <>,
	Linux Kernel list <>
Subject: Re: DMA mapping API for non-system memory pools
Date: Fri, 09 Feb 2007 18:53:29 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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).


  reply	other threads:[~2007-02-09 23:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 23:33 Kumar Gala
2007-02-09 23:53 ` James Bottomley [this message]
2007-02-09 23:54 ` Matthew Jacob

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: DMA mapping API for non-system memory pools' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).