From: Rob Duncan <rduncan@tesla.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: More snd_pcm_ioplug_avail_update() questions
Date: Thu, 26 Jul 2018 07:19:19 -0700 [thread overview]
Message-ID: <dw77emfu06cc60.fsf@tesla.com> (raw)
In-Reply-To: <s5hzhyev5oj.wl-tiwai@suse.de>
At 00:04 on Thu, Jul 26 2018, Takashi wrote:
>> Is it required that all available data has been committed between calls
>> to snd_pcm_ioplug_avail_update() on an IO plugin capture stream?
>
> Yes, the capture data is committed.
> The snd_pcm_ioplug_hw_ptr_update() should have reported the amount of
> data the slave PCM can actually transfer. Hence the transfer call
> thereafter must fulfill the whole requested data.
But what I see is that snd_pcm_rate_avail_update() commits data in the
slave PCM in units of slave->period_size (via
snd_pcm_rate_grab_next_period()), which means that if there is a partial
period in the slave PCM mmap it will not be committed.
In other words, not all the available data will be commmitted before the
next call to snd_pcm_ioplug_avail_update(). This means that the data
will be discarded the next time that snd_pcm_ioplug_avail_update() is
called.
Rob.
next prev parent reply other threads:[~2018-07-26 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 21:52 More snd_pcm_ioplug_avail_update() questions Rob Duncan
2018-07-26 7:04 ` Takashi Iwai
2018-07-26 14:19 ` Rob Duncan [this message]
2018-07-26 14:37 ` Takashi Iwai
2018-07-26 15:02 ` Rob Duncan
2018-07-26 15:14 ` Takashi Iwai
2018-07-30 18:55 ` Rob Duncan
2018-07-31 8:21 ` 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=dw77emfu06cc60.fsf@tesla.com \
--to=rduncan@tesla.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.