linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, cjg@cruxppc.org
Subject: [PATCH 0/3] ALSA fixes for non-coherent ppc32
Date: Wed, 18 Jun 2008 12:38:31 +0200	[thread overview]
Message-ID: <s5h1w2vc9js.wl%tiwai@suse.de> (raw)

Hi,

I've tried to renew the fixes of ALSA issues about non-coherent DMA
memories.  The last patch worked for SG-buffers somehow but would
result in a problem if many pages are allocated because of
dma_alloc_coherent() handling.  Now, I chose a more simpler
workaround: the SG-buffers are handled as simple continuous buffers.

This time I split the patches to several parts.  The first patch
contains a very lazy dma_mmap_coherent() implementation for ppc32.
The next patch adds the call of dma_mmap_coherent() for the default
mmap of ALSA PCM.  And the last one is to add the conversion of
SG-buffer handling as above.

The patches are created against the latest ALSA tree, and the last
patch won't be applicable fully to 2.6.26-rc6.  But, it's only for
snd-hda-intel and there is no PPC32 hardware supporting this, AFAIK.
So just ignore the reject.

The patches are found also on my git tree, dma-fix branch of
    git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git


Any comments and test reports are appreciated, especially about
dma_mmap_coherent() addition.


thanks,

Takashi

             reply	other threads:[~2008-06-18 10:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 10:38 Takashi Iwai [this message]
2008-06-18 10:40 ` [PATCH 1/3] ppc: Add dma_mmap_coherent() for PPC32 Takashi Iwai
2008-06-18 10:41 ` [PATCH 2/3] ALSA: Fix mapping of DMA buffers Takashi Iwai
2008-06-18 10:42 ` [PATCH 3/3] ALSA: Fix SG-buffer DMA with non-coherent architectures Takashi Iwai
2008-07-09  8:31 ` [PATCH 0/3] ALSA fixes for non-coherent ppc32 Gerhard Pircher
2008-07-09  8:55   ` Benjamin Herrenschmidt
2008-07-09 17:31     ` Takashi Iwai
2008-07-09 20:06       ` Benjamin Herrenschmidt
2008-07-09 17:27   ` Takashi Iwai

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=s5h1w2vc9js.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=cjg@cruxppc.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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).