From: Takashi Iwai Subject: Re: timestamp update when no hw delta Date: Wed, 25 Oct 2017 08:30:55 +0200 Message-ID: References: <20171010121459.GF24037@lnxhenriken2.se.axis.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 88814266A0C for ; Wed, 25 Oct 2017 08:30:56 +0200 (CEST) In-Reply-To: <20171010121459.GF24037@lnxhenriken2.se.axis.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: Henrik Eriksson Cc: alsa-devel@alsa-project.org, Pierre-Louis Bossart List-Id: alsa-devel@alsa-project.org On Tue, 10 Oct 2017 14:14:59 +0200, Henrik Eriksson wrote: > > Hi > > I am looking into commit 3179f62001880e588e229db3006a59ad87b7792a > ("ALSA: core: add .get_time_info"), which, if I understand the code > correctly, changed the behaviour of timestamps. Before this change, > snd_pcm_update_hw_ptr0() just returned if the no_delta_check showed that > the hw_ptr had not changed. With this change it will update the > timestamps before returning. > > Was this intended, and if so does anyone have any insights to why? The > original behaviour to not update the timestamps when the hw position has > not changed seems more correct to me, but I am new to this code. Pierre is the best person to answer this, but AFAIK, the intention is to allow more fine-grained timestamp, and it's finer than the sample rate. That is, you want to know the continuous (wallclock) time stamp even between two PCM pulses, which allows more exact synchronization of the PCM timeline and the system/network timeline. thanks, Takashi