From: Takashi Iwai Subject: Re: [PATCH 0/2 v2] alsa-lib: dynamically adapt the avail_min on the slave Date: Mon, 02 Jan 2017 15:01:10 +0100 Message-ID: References: <20161219033751.30848-1-jiada_wang@mentor.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 39C8626698C for ; Mon, 2 Jan 2017 15:01:12 +0100 (CET) In-Reply-To: <20161219033751.30848-1-jiada_wang@mentor.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Jiada Wang Cc: wens@csie.org, broonie@kernel.org, apape@de.adit-jv.com, lgirdwood@gmail.com, alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On Mon, 19 Dec 2016 04:37:49 +0100, Jiada Wang wrote: > > 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. Thanks, applied both patches now. Takashi > > Andreas Pape (2): > plugin: dynamically update avail_min on slave > rate: dynamic update avail_min on slave > > src/pcm/pcm_plugin.c | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++- > src/pcm/pcm_plugin.h | 3 +++ > src/pcm/pcm_rate.c | 2 +- > 3 files changed, 67 insertions(+), 2 deletions(-) > > -- > 2.9.3 >