From: Timur Tabi <timur@freescale.com>
To: Takashi Iwai <tiwai@suse.de>, clemens@ladisch.de
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Possible problem with snd_pcm_oss_sync()
Date: Wed, 21 May 2008 09:15:06 -0500 [thread overview]
Message-ID: <48342E6A.6060005@freescale.com> (raw)
In-Reply-To: <s5hr6bwvsvl.wl%tiwai@suse.de>
Takashi Iwai wrote:
> The sync ioctl is to block the operation until all samples are
> played. But, it's a bit strange that the stream stops after this. It
> should be an underrun instead (and OSS recovers by itself).
I figured it out. When the application starts, my driver gets a call to the
_hw_params and _prepare functions. When the app calls SNDCTL_DSP_SYNC, those
two functions get called again. At that point, the DMA controller gets
re-programmed. For some reason, it doesn't like that. The DMA never actually
starts.
I moved some of the DMA programming code to my _open function (where it belongs,
anyway), and now bplay works.
Well, almost. After about a second into playback, it skips a little bit. And
then about 4-5 seconds later, bplay calls SNDCTL_DSP_SYNC, and that causes
playback to pause for about a second.
I need to figure out why bplay is calling sync, and why the audio skips in the
beginning.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2008-05-21 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 16:03 Possible problem with snd_pcm_oss_sync() Timur Tabi
2008-05-20 18:57 ` Timur Tabi
2008-05-21 11:25 ` Clemens Ladisch
2008-05-21 10:44 ` Takashi Iwai
2008-05-21 14:15 ` Timur Tabi [this message]
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=48342E6A.6060005@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--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.