From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre-Louis Bossart Subject: Re: [PATCH 2/2] ALSA: hda: support for wallclock timestamps Date: Wed, 13 Jun 2012 23:57:59 -0500 Message-ID: <4FD96F57.3090502@linux.intel.com> References: <1339619192-2733-1-git-send-email-pierre-louis.bossart@linux.intel.com> <1339619192-2733-3-git-send-email-pierre-louis.bossart@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by alsa0.perex.cz (Postfix) with ESMTP id 2E7BB244AD for ; Thu, 14 Jun 2012 06:58:02 +0200 (CEST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org On 6/13/2012 10:32 PM, Wang Xingchao wrote: > I'm afraid you donot think much about the Wall Clock Counter register, > the counter will roll over to 0 within 179s under 24Mhz. Another case > maybe BCLK stop and controller reset. thanks --xingchao Hi Xingchao, all cycle counters will wrap around at some point, the HDAudio wall clock isn't an exception. As long as you have 2 periods or events per 179s, the wrap-around can be detected without any issues. It's explicitely handled in the code. If the BCLK stops, then there's no real audio transfer happening, is there? Likewise the controller reset does not matter since we re-init during a trigger. I don't see any of these points as show-stoppers. The HDAudio spec clearly mentions that such a wall clock should be used for synchronization with other devices, and I am enabling just that. Regards, -Pierre