From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars-Peter Clausen Subject: ASoC: tegra: Does the PCM_TRIGGER_{PAUSE, RESUME} emulation really work? Date: Fri, 22 Mar 2013 17:26:00 +0100 Message-ID: <514C8618.9070307@metafoo.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from smtp-out-087.synserver.de (smtp-out-087.synserver.de [212.40.185.87]) by alsa0.perex.cz (Postfix) with ESMTP id 9F5152651A0 for ; Fri, 22 Mar 2013 17:23:53 +0100 (CET) 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: Stephen Warren , Laxman Dewangan Cc: Linux-ALSA List-Id: alsa-devel@alsa-project.org Hi, The tegra pcm driver tries to emulate SNDRV_PCM_TRIGGER_PAUSE and SNDRV_PCM_TRIGGER_RESUME. By passing SNDRV_PCM_TRIGGER_START and SNDRV_PCM_TRIGGER_STOP to snd_dmaengine_pcm_trigger. But does this really work? The old non-dmaengine based driver implemented this properly. I'd reset the dma position pointer for SNDRV_PCM_TRIGGER_START, but keep it where it was for SNDRV_PCM_TRIGGER_RESUME. But as far as I can see with the dmaengine based driver the pointer always gets reset to 0 for both SNDRV_PCM_TRIGGER_START and SNDRV_PCM_TRIGGER_RESUME. - Lars