From: Mark Brown Subject: Re: [PATCH 6/6] ASoC/mpc5200: Add fudge factor to value reported by .pointer() Date: Sat, 7 Nov 2009 18:11:54 +0000 Message-ID: <20091107181153.GA31789@sirena.org.uk> References: <20091107081631.18908.82921.stgit@angua> <20091107083448.18908.80366.stgit@angua> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from cassiel.sirena.org.uk (cassiel.sirena.org.uk [80.68.93.111]) by alsa0.perex.cz (Postfix) with ESMTP id 8D5C42466D for ; Sat, 7 Nov 2009 19:12:05 +0100 (CET) Content-Disposition: inline In-Reply-To: <20091107083448.18908.80366.stgit@angua> 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: Grant Likely Cc: alsa-devel@alsa-project.org, linuxppc-dev@lists.ozlabs.org, lrg@slimlogic.co.uk List-Id: alsa-devel@alsa-project.org On Sat, Nov 07, 2009 at 01:34:55AM -0700, Grant Likely wrote: > ALSA playback seems to be more reliable if the .pointer() hook reports > a value slightly into the period, rather than right on the period > boundary. This patch adds a fudge factor of 1/4 the period size > to better estimate the actual position of the DMA engine in the > audio buffer. It occurs to me that in terms of dealing with what's going on here this probably is achieving exactly the same effect as Jon's code in that it tells ALSA that things are a bit ahead of where the buffer started.