All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: SNDRV_PCM_INFO_MMAP - what do I need for it?
Date: Wed, 16 Jan 2008 13:06:00 -0600	[thread overview]
Message-ID: <478E5598.9060306@freescale.com> (raw)
In-Reply-To: <s5hy7apr7s0.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Wed, 16 Jan 2008 09:17:57 -0600,
> Timur Tabi wrote:
>> My 8610 ASoC driver has this:
>>
>> static const struct snd_pcm_hardware fsl_dma_hardware = {
>>
>> 	.info   		= SNDRV_PCM_INFO_INTERLEAVED,
>>
>> This means that MMAP is not enabled.
>>
>> I understand what MMAP is, but not from an ALSA driver perspective.  If I change 
>> the above line to this:
>>
>> 	.info   		= SNDRV_PCM_INFO_INTERLEAVED | SNDRV_PCM_INFO_MMAP | 
>> SNDRV_PCM_INFO_MMAP_VALID,
>>
>> what does ALSA do differently?  Do I need to define any new functions?  From an 
>> application perspective, what is different?
> 
> It means that the driver supports mmap access to the PCM buffer.
> 
> In some cases, you need to implement a proper mmap callback.  For
> example, when the coheret (dma) pages are allocated via
> dma_alloc_coherent and used for the PCM buffer, you need mmap callback
> for ARM, at least because the default mmap handler in the PCM core
> doesn't work for ARM.  In this case, prepare your own mmap callback
> and pass it to pcm ops.  It should call simply dma_mmap_coherent()
> appropriately.

The default mmap handler in the PCM core is snd_pcm_default_mmap()?

How can I know whether this function works?  Can I just add those two flags to 
my .info line, and then .... ?  Is there an ALSA mmap test utility?

>> Also, does DMIX need MMAP support?
> 
> Yes, mandatory.

So just to be clear: the fact that I do *not* have "SNDRV_PCM_INFO_MMAP | 
SNDRV_PCM_INFO_MMAP_VALID" defined in snd_pcm_hardware.info is the reason why I 
get this error message:

root@MPC8610HPCD:/home/demo_files/mp3# alsaplayer -o alsa -q -F 48000
-d plug:dmix ./527182737.mp3 &
[1] 3224
root@MPC8610HPCD:/home/demo_files/mp3# ALSA lib
pcm_direct.c:874:(snd_pcm_direct_initialize_slave) slave plugin does not
support mmap interleaved or mmap noninterleaved access
ALSA lib pcm_dmix.c:878:(snd_pcm_dmix_open) unable to initialize slave
snd_pcm_open: Invalid argument (plug:dmix)
Failed to initialize plugin!
...

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2008-01-16 19:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 15:17 SNDRV_PCM_INFO_MMAP - what do I need for it? Timur Tabi
2008-01-16 17:37 ` Takashi Iwai
2008-01-16 19:06   ` Timur Tabi [this message]
2008-01-16 19:40     ` Timur Tabi
2008-01-16 19:45     ` Trent Piepho

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=478E5598.9060306@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.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 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.