Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: alsa-devel@alsa-project.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: DMA HW bug in MX2x platforms?
Date: Fri, 31 Jul 2009 11:52:51 +0200	[thread overview]
Message-ID: <20090731095251.GF13236@buzzloop.caiaq.de> (raw)
In-Reply-To: <eedb5540907240037u2cb8fbfap84f02727621261d9@mail.gmail.com>

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?

Daniel

  reply	other threads:[~2009-07-31  9:52 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 [this message]
2009-07-31 10:01   ` Mark Brown

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=20090731095251.GF13236@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=alsa-devel@alsa-project.org \
    --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