Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Giuseppe Coviello <cjg@cruxppc.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org
Subject: Re: ALSA fixes for non-coherent archs (Re: [PATCH] Sam440ep support)
Date: Mon, 19 May 2008 19:23:10 +0200	[thread overview]
Message-ID: <1211217790.2037.3.camel@marquez.cjg.home> (raw)
In-Reply-To: <s5hr6c5ax6a.wl%tiwai@suse.de>

On mer, 14/05/2008 14.26 +0200, Takashi Iwai wrote:
[cut]
> OK, here is another patch for testing.  Since I lost my old patch
> somewhere (and it's not worth to dig the archive), I wrote it up
> quickly from scratch.  This version should cover both SG and non-SG
> buffers.  It's against the latest git tree.
> 
> The patch adds a hackish verison of dma_mmap_coherent() for some
> architectures in sound/core/pcm_native.c.  I'm not sure whether this
> works.  I just tested it on X86.  It'd be appreciated if someone can
> test this.
> 
> Also, this disables HDSPM driver for non-X86/IA64 since the driver has
> own copy and silence methods that are incompatible with the new
> SG-buffer data.
> 
> 
> And, yes, I know we need to clean up huge messes in ALSA memory
> handling routines.  But, let's fix obvious bugs before starting a big
> rewrite...
> 

I've just tested this patch on the sam440ep and it works great (and
sounds great, of course). I had also to make the following changes:

Signed-off-by: Giuseppe Coviello <gicoviello@gmail.com>

diff --git a/sound/pci/cs4281.c b/sound/pci/cs4281.c
index 7556fd9..f5f208e 100644
--- a/sound/pci/cs4281.c
+++ b/sound/pci/cs4281.c
@@ -952,6 +952,9 @@ static struct snd_pcm_ops snd_cs4281_playback_ops = {
 	.prepare =	snd_cs4281_playback_prepare,
 	.trigger =	snd_cs4281_trigger,
 	.pointer =	snd_cs4281_pointer,
+	.copy =         snd_pcm_sgbuf_ops_copy,
+	.silence =      snd_pcm_sgbuf_ops_silence,
+       .page =         snd_pcm_sgbuf_ops_page,
 };
 
 static struct snd_pcm_ops snd_cs4281_capture_ops = {
@@ -963,6 +966,8 @@ static struct snd_pcm_ops snd_cs4281_capture_ops = {
 	.prepare =	snd_cs4281_capture_prepare,
 	.trigger =	snd_cs4281_trigger,
 	.pointer =	snd_cs4281_pointer,
+	.copy =         snd_pcm_sgbuf_ops_copy,
+       .page =         snd_pcm_sgbuf_ops_page,
 };
 
 static int __devinit snd_cs4281_pcm(struct cs4281 * chip, int device,

  parent reply	other threads:[~2008-05-19 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a265241c0805051123h595123edrd46bf65a8099c3c2@mail.gmail.com>
     [not found] ` <6DA6B1DA-11B5-4B89-88AD-561B4D17B33B@kernel.crashing.org>
     [not found]   ` <20080505195054.172000@gmx.net>
     [not found]     ` <1210031058.21644.120.camel@pasglop>
     [not found]       ` <20080506075115.269150@gmx.net>
     [not found]         ` <1210063719.21644.162.camel@pasglop>
     [not found]           ` <20080506091622.269180@gmx.net>
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 [this message]
2008-05-20 12:48                 ` 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=1211217790.2037.3.camel@marquez.cjg.home \
    --to=cjg@cruxppc.org \
    --cc=alsa-devel@alsa-project.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