alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jiada Wang <jiada_wang@mentor.com>
To: lgirdwood@gmail.com, broonie@kernel.org, wens@csie.org
Cc: jiada_wang@mentor.com, alsa-devel@alsa-project.org, apape@de.adit-jv.com
Subject: [PATCH 0/2] alsa-lib: dynamically adapt the avail_min on the slave
Date: Thu, 10 Nov 2016 16:34:41 +0900	[thread overview]
Message-ID: <20161110073443.1192-1-jiada_wang@mentor.com> (raw)

When configuring avail_min to multiple of slave period size it can happen
that user waits one slave period longer than needed for available data. 
Root cause is implicit grabbing of slave samples in avail_update operation. 
On next entering poll, the slave will wait for the avail_min threshold 
reached again, as he is not aware that there are already pending samples 
in the above layer which are not yet provided to user. 
Solution is to dynamically adapt the avail_min on the slave. 


Andreas Pape (2):
  plugin: dynamically update avail_min on slave
  rate: dynamic update avail_min on slave

 src/pcm/pcm_plugin.c | 48 +++++++++++++++++++++++++++++++++++++++++++++++-
 src/pcm/pcm_plugin.h |  3 +++
 src/pcm/pcm_rate.c   |  2 +-
 3 files changed, 51 insertions(+), 2 deletions(-)

-- 
2.9.3

             reply	other threads:[~2016-11-10  7:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10  7:34 Jiada Wang [this message]
2016-11-10  7:34 ` [PATCH 1/2] plugin: dynamically update avail_min on slave Jiada Wang
2016-11-10  7:34 ` [PATCH 2/2] rate: dynamic " Jiada Wang
2016-11-11 11:10 ` [PATCH 0/2] alsa-lib: dynamically adapt the avail_min on the slave Takashi Iwai
2016-11-28  8:31   ` Jiada Wang
2016-12-09  5:41   ` Jiada Wang

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=20161110073443.1192-1-jiada_wang@mentor.com \
    --to=jiada_wang@mentor.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=apape@de.adit-jv.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=wens@csie.org \
    /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;
as well as URLs for NNTP newsgroup(s).