Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: daniel.car@cox.net
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Looking for help with dmix plug-in on ARM
Date: Fri, 09 Feb 2007 13:06:39 +0100	[thread overview]
Message-ID: <s5hps8jo7qo.wl%tiwai@suse.de> (raw)
In-Reply-To: <15711510.1170960250793.JavaMail.root@fed1wml07.mgt.cox.net>

At Thu, 8 Feb 2007 10:44:10 -0800,
<daniel.car@cox.net> wrote:
> 
> Hi,
> 
> I'm working on an unannounced SOC audio driver on an ARM system.  I have a problem were audio works fine with out dmix, but when I try to use dmix no audio data gets to the driver.  The dmix plug-in does work when attaching external usb audio device.  Trying to use dmix so that more then one application can generate audio simultaneously.
> 
> If I try with version 1.0.11 of ALSA the audio driver doesn't receive any data after the snd_pcm_period_elapsed() function call.  If I try with version 1.0.13 of ALSA, aplay returns an error saying: 
> # aplay -D hw:0,0 pcm48khz_2ch_stereo.wav open_stream success
>   Playing WAVE 'pcm48khz_2ch_stereo.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
>   aplay: set_params:882: Broken configuration for this PCM: no configurations available
> 
> I'm planning on building a debug version of 1.0.14rc2 and tracing thru the code to see why aplay fails.  Is there a better way to debug this?  Are there any tricks for building ALSA with debug info?

So, actually it's a problem of driver / alsa-lib hw layer rather than
dmix?  You can get more verbose messages by setting LIBASOUND_DEBUG
variable.  See alsa-lib/NOTES for details.

> Here is how the driver is set up:
> static snd_pcm_hardware_t snd_oloriver_playback_hw = {
>  .info = (SNDRV_PCM_INFO_MMAP | SNDRV_PCM_INFO_INTERLEAVED |
> 	   SNDRV_PCM_INFO_MMAP_VALID),
>  .formats 	    = SNDRV_PCM_FMTBIT_S16_LE,
>   .rates 	    = SNDRV_PCM_RATE_48000,
>   .rate_min	    = 48000, 
>   .rate_max	    = 48000,
>   .channels_min     = 2,
>   .channels_max     = 2,
>   .buffer_bytes_max = 65536,
>   .period_bytes_min = 32768,
>   .period_bytes_max = 32768,
>   .periods_min 	    = 2,
>   .periods_max 	    = 2,

My rough guess is that the buffer and period size constraints are too
restrictive.  You can try to pass the exact period/buffer sizes to
aplay via --period-size=8192 --buffer-size=16384 options.


Takashi

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2007-02-09 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 18:44 Looking for help with dmix plug-in on ARM daniel.car
2007-02-09 12:06 ` Takashi Iwai [this message]
2007-02-26 14:13   ` Daniel Cardenas
2007-02-27 21:25     ` Daniel Cardenas
2007-03-03  3:54       ` Daniel Cardenas
2007-03-07 22:54       ` 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=s5hps8jo7qo.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=daniel.car@cox.net \
    /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