From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: DMA HW bug in MX2x platforms? Date: Fri, 31 Jul 2009 11:01:00 +0100 Message-ID: <20090731100059.GA17091@sirena.org.uk> References: <20090731095251.GF13236@buzzloop.caiaq.de> 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 8B3BE243F8 for ; Fri, 31 Jul 2009 12:01:01 +0200 (CEST) Content-Disposition: inline In-Reply-To: <20090731095251.GF13236@buzzloop.caiaq.de> 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: Daniel Mack Cc: alsa-devel@alsa-project.org, javier Martin , linux-arm-kernel@lists.arm.linux.org.uk List-Id: alsa-devel@alsa-project.org On Fri, Jul 31, 2009 at 11:52:51AM +0200, Daniel Mack wrote: > On Fri, Jul 24, 2009 at 09:37:33AM +0200, javier Martin wrote: > > I am currently working on an ASoC driver for mx2x platforms. I am > > porting an old working ASoC driver for 2.6.22 + Freescale BSP kernel > > to current 2.6.30 kernel. > Will the SSI/I2S part be compatible to mx3 platforms or are the register > set too different? They should be able to share the same SSI driver; the DMA is radically different so there'll be some per-CPU code to interact with the DMA driver but the bulk of it should be transferrable.