From: Takashi Iwai Subject: Re: Improving status timestamp accuracy Date: Mon, 06 Jun 2016 10:34:01 +0200 Message-ID: References: <5752A005.2050309@gmail.com> <5753FFF0.3050200@gmail.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 8D49C2656F6 for ; Mon, 6 Jun 2016 10:34:01 +0200 (CEST) In-Reply-To: <5753FFF0.3050200@gmail.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: Alan Young Cc: Raymond Yau , alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On Sun, 05 Jun 2016 12:33:20 +0200, Alan Young wrote: > > Regardless of what value of DMA_RESIDUE_GRANULARITY_xxx that a driver > claims to support, it is not really defined how fine a burst might > be. So the end result is, from the point of view of audio, that the > resulting position obtained by the pointer() call is pretty > inaccurate. Hence my proposal to attempt to improve the accuracy of > the pcm_status() result given the above constraints. Well, the subject appears misleading. What you want isn't the audio timestamp accuracy. From API POV, the accurate position is calculated via the (additional) delay. So, what you want is rather the accurate position delay accounting, and the audio timestamp is merely one of the ways to achieve that. Takashi