From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: issue of shdma-base library Date: Tue, 9 Oct 2012 15:46:46 +0900 Message-ID: <20121009064643.GR8237@opensource.wolfsonmicro.com> References: <506A7E48.3060701@jinso.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from opensource.wolfsonmicro.com (opensource.wolfsonmicro.com [80.75.67.52]) by alsa0.perex.cz (Postfix) with ESMTP id 5366C2615CF for ; Tue, 9 Oct 2012 08:46:56 +0200 (CEST) Content-Disposition: inline In-Reply-To: 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: Guennadi Liakhovetski Cc: Shimoda Yoshihiro , alsa-devel@alsa-project.org, Liam Girdwood , Morimoto Kuninori , "Do Q.Thang" List-Id: alsa-devel@alsa-project.org On Wed, Oct 03, 2012 at 02:33:50PM +0200, Guennadi Liakhovetski wrote: > Subject: [PATCH] ASoC: fsi: don't reschedule DMA from an atomic context > > shdma doesn't support transfer re-scheduling or triggering from callbacks > or from atomic context. The fsi driver issues DMA transfers from a tasklet > context, which is a bug. To fix it convert tasklet to a work. Applied, thanks.