From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Daniel Mack <daniel@caiaq.de>
Cc: alsa-devel@alsa-project.org,
javier Martin <javier.martin@vista-silicon.com>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: DMA HW bug in MX2x platforms?
Date: Fri, 31 Jul 2009 11:01:00 +0100 [thread overview]
Message-ID: <20090731100059.GA17091@sirena.org.uk> (raw)
In-Reply-To: <20090731095251.GF13236@buzzloop.caiaq.de>
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.
prev parent reply other threads:[~2009-07-31 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 7:37 DMA HW bug in MX2x platforms? javier Martin
2009-07-31 9:52 ` Daniel Mack
2009-07-31 10:01 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090731100059.GA17091@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=daniel@caiaq.de \
--cc=javier.martin@vista-silicon.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox