From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752628AbbJTNBf (ORCPT ); Tue, 20 Oct 2015 09:01:35 -0400 Received: from smtp-out-210.synserver.de ([212.40.185.210]:1039 "EHLO smtp-out-188.synserver.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752352AbbJTNBb (ORCPT ); Tue, 20 Oct 2015 09:01:31 -0400 X-SynServer-TrustedSrc: 1 X-SynServer-AuthUser: lars@metafoo.de X-SynServer-PPID: 3082 Message-ID: <56263B27.9000106@metafoo.de> Date: Tue, 20 Oct 2015 15:01:27 +0200 From: Lars-Peter Clausen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: Takashi Iwai CC: Vinod Koul , alsa-devel@alsa-project.org, Russell King , Shengjiu Wang , Dan Williams , Jonah Petri , Matt Campbell , Qiao Zhou , Kuninori Morimoto , dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 4/4] ALSA: pcm_dmaengine: Properly synchronize DMA on shutdown References: <1445334391-12272-1-git-send-email-lars@metafoo.de> <1445334391-12272-5-git-send-email-lars@metafoo.de> <56262810.3040201@metafoo.de> In-Reply-To: <56262810.3040201@metafoo.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [...] > I've tested this series with xrun injection and some modifications to the > DMA driver to always trigger the race condition when the stream is stopped. > And I've not seen any issues after the transfer re-started. (There is a > dead-lock condition though but that does not seem to be related to this series) Turns out that was a bug in the DMA driver that caused snd_pcm_period_elapsed() to be called on the TRIGGER_START path. So the ALSA side seems to be good.