linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: linuxppc-dev@ozlabs.org, cjg@cruxppc.org
Subject: Re: [PATCH] Sam440ep support
Date: Tue, 06 May 2008 21:25:53 +1000	[thread overview]
Message-ID: <1210073153.21644.175.camel@pasglop> (raw)
In-Reply-To: <s5hlk2nd6r5.wl%tiwai@suse.de>


On Tue, 2008-05-06 at 13:14 +0200, Takashi Iwai wrote:
> > sg allocations are usually lists of page, so virt_to_page shouldn't
> be a
> > problem in the first place, though we still need some way to get the
> > right prot attributes.
> 
> The problem is that ALSA SG buffer is composed from pages allocated
> via dma_alloc_coherent(), and the pages are retrieved via virt_to_page
> for DMA pages, as found in sound/core/sgbuf.c.
> 
> I didn't care about SG-buffer cases in my initial patch, and it's a
> bit messy.  The current code requires page lists becasue it calls
> vmap() to get a virtually linear buffer.

Hrm... the problem is that you aren't supposed to make up sglists with
the result of dma_alloc_coherent... It might be a limitation of our core
DMA API, but that's we have to deal with today..

If you're going to make up sglists and call vmap, you should allocate
pages with normal GFP. If that is a problem vs. DMA'bility of those
pages, then ... we have a problem :-)

I don't think we can easily update the DMA API at this stage. What we
could do is provide a way to retrieve the struct page array from the
result of dma_alloc_coherent...

Ben.

  reply	other threads:[~2008-05-06 11:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 18:23 [PATCH] Sam440ep support Giuseppe Coviello
2008-05-05 18:27 ` Kumar Gala
2008-05-05 19:50   ` Gerhard Pircher
2008-05-05 23:44     ` Benjamin Herrenschmidt
2008-05-06  7:51       ` Gerhard Pircher
2008-05-06  8:48         ` Benjamin Herrenschmidt
2008-05-06  9:16           ` Gerhard Pircher
2008-05-06 10:12             ` Benjamin Herrenschmidt
2008-05-06 11:14               ` Takashi Iwai
2008-05-06 11:25                 ` Benjamin Herrenschmidt [this message]
2008-05-06 11:27                   ` Benjamin Herrenschmidt
2008-05-06 11:31                   ` Takashi Iwai
2008-05-06 11:34                     ` Benjamin Herrenschmidt
2008-05-14 12:26             ` ALSA fixes for non-coherent archs (Re: [PATCH] Sam440ep support) Takashi Iwai
2008-05-14 12:50               ` Gerhard Pircher
2008-05-14 21:01               ` Gerhard Pircher
2008-05-15  5:42                 ` Takashi Iwai
2008-05-19 17:23               ` Giuseppe Coviello
2008-05-20 12:48                 ` Takashi Iwai
2008-05-05 23:38   ` [PATCH] Sam440ep support Benjamin Herrenschmidt
2008-05-05 18:54 ` Josh Boyer
2008-05-05 23:40   ` Benjamin Herrenschmidt
2008-05-06  0:09     ` Josh Boyer
2008-05-05 23:36 ` Benjamin Herrenschmidt
2008-05-06  4:18   ` Sean MacLennan
2008-05-06 16:37 ` Giuseppe Coviello
2008-05-09 15:53   ` Giuseppe Coviello
2008-05-09 20:26     ` Josh Boyer
2008-05-19 12:47   ` Josh Boyer
2008-05-19 15:20     ` Giuseppe Coviello
2008-05-20 12:50       ` Josh Boyer
2008-05-20 13:34         ` Josh Boyer
2008-05-22 17:51           ` Giuseppe Coviello

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=1210073153.21644.175.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=cjg@cruxppc.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).