From: Stas Sergeev <stsp@list.ru>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: ALSA devel <alsa-devel@alsa-project.org>,
"Gabriel M. Beddingfield" <gabrbedd@gmail.com>,
stsp@users.sourceforge.net
Subject: Re: [PATCH] ASoC: define playback and capture streams in dummy codec
Date: Fri, 12 Apr 2013 23:19:15 +0400 [thread overview]
Message-ID: <51685E33.4080401@list.ru> (raw)
In-Reply-To: <51683C7F.6080803@metafoo.de>
12.04.2013 20:55, Lars-Peter Clausen пишет:
> On 04/12/2013 06:37 PM, Stas Sergeev wrote:
>> Thanks for an explanation!
>> But what happens when the DAI is considered mute
>> by the effect of such intersection?
>> From what I can see, no callbacks from the DAI driver
>> are called in this case (this is expected), but no
>> error is returned to userspace, and, more importantly,
>> the playback speed is still correct, so the userspace
>> can get a playback position as if the playback is fine.
>> While during the normal playback, if I stop calling
>> snd_pcm_period_elapsed(), userspace is no longer getting
>> the right position.
>> That's why I am confused, I can't easily explain this
>> "no sound but otherwise fine playback" effect, so I am
>> a bit reluctant to try explaining this in a commit msg.
>> Are there are some fallbacks? Such as when the DAI is
>> considered mute, it gets somehow emulated, with the use
>> of the system clock for correct timing etc?
> That's actually a bit strange indeed, since you should get an error when you
> try to open the pcm device.
Ah great!
Next week I'll double-check that the fall-back is actually
in userspace (in an android media stack perhaps), and
that will be enough info for the reasonable commit msg. :)
Thanks for your help!
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2013-04-12 19:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 10:53 [PATCH] ASoC: define playback and capture streams in dummy codec Stas Sergeev
2013-04-12 10:59 ` Mark Brown
2013-04-12 14:19 ` Stas Sergeev
2013-04-12 15:13 ` Gabriel M. Beddingfield
2013-04-12 15:20 ` Stas Sergeev
2013-04-12 15:24 ` Gabriel M. Beddingfield
2013-04-16 16:34 ` Stas Sergeev
2013-04-12 15:31 ` Lars-Peter Clausen
2013-04-12 16:37 ` Stas Sergeev
2013-04-12 16:55 ` Lars-Peter Clausen
2013-04-12 19:19 ` Stas Sergeev [this message]
2013-04-17 12:34 ` Stas Sergeev
2013-04-17 13:31 ` Mark Brown
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=51685E33.4080401@list.ru \
--to=stsp@list.ru \
--cc=alsa-devel@alsa-project.org \
--cc=gabrbedd@gmail.com \
--cc=lars@metafoo.de \
--cc=stsp@users.sourceforge.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