All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: "Alexander E. Patrakov" <patrakov@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] [ALSA] mpc8610: Add mmap support
Date: Thu, 17 Jan 2008 10:31:37 -0600	[thread overview]
Message-ID: <478F82E9.1050809@freescale.com> (raw)
In-Reply-To: <478F8129.5030408@gmail.com>

Alexander E. Patrakov wrote:
> Timur Tabi wrote:
>> Enable mmap support in the MPC8610 ASoC driver.  The driver can use 
>> ALSA's
>> default mmap functionality, it was just not enabled previously.
>>
>> Signed-off-by: Timur Tabi <timur@freescale.com>
> 
> [sorry, I may be completely wrong below about the .page callback purpose 
> - in this case, just confirm that the testcase works]
> 
> Hm, the "struct snd_pcm_ops fsl_dma_ops" doesn't contain the .page 
> callback. With saa7134-alsa, this led to the "device claims to support 
> mmap but actually doesn't work" bug, see the following subthread:

Isn't that an ARM chip?  The default MMAP handler in ALSA doesn't support ARM, 
but it works for PowerPC.

> http://mailman.alsa-project.org/pipermail/alsa-devel/2007-October/003773.html 
> 
> 
> IOW: have you actually tested that the following commands work (X,Y 
> refer to the FSL chip)?
> 
> aplay -M -D hw:X,Y sample.wav
> arecord -f cd -M -D:X,Y capture.wav

I haven't tried record, but I did try playback, and it worked.  Without this 
patch, adding -M gives me this error:

aplay: set_params:852: Access type not available

After applying this patch, playback works fine.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2008-01-17 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 15:06 [PATCH] [ALSA] mpc8610: Add mmap support Timur Tabi
2008-01-17 16:24 ` Alexander E. Patrakov
2008-01-17 16:31   ` Timur Tabi [this message]
2008-01-17 16:45     ` Takashi Iwai
2008-01-17 17:00     ` Alexander E. Patrakov
2008-01-17 21:40     ` Trent Piepho
2008-01-17 21:41       ` Timur Tabi

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=478F82E9.1050809@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=patrakov@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.