From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] Add i.MX sound support
Date: Wed, 25 Nov 2009 16:41:03 +0100 [thread overview]
Message-ID: <1259163666-30344-1-git-send-email-s.hauer@pengutronix.de> (raw)
Hi All,
Here is the second version of the patches to add i.MX sound support.
This time I haven't included ARM related patches, so this series should
be safe to apply.
I skipped the mc13783 driver since I'm not ready integrating the comments
from Mark.
The main change in the driver is that I splitted out the transport from
the driver, so it should be easy to add another transport layer to the
driver when SDMA support is merged. I hopefully also addressed the other
comments from Mark.
Sascha
next reply other threads:[~2009-11-25 15:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 15:41 Sascha Hauer [this message]
2009-11-25 15:41 ` [PATCH 1/3] ASoC: Add a new imx-ssi sound driver Sascha Hauer
2009-11-25 15:41 ` [PATCH 2/3] ASoC: add phycore-ac97 sound support Sascha Hauer
2009-11-25 15:41 ` [PATCH 3/3] ASoC i.MX: remove old i.MX driver Sascha Hauer
2009-11-25 15:53 ` Mark Brown
2009-11-25 15:43 ` [PATCH 2/3] ASoC: add phycore-ac97 sound support Mark Brown
2009-11-25 15:58 ` [PATCH 1/3] ASoC: Add a new imx-ssi sound driver Mark Brown
2009-11-30 16:40 ` javier Martin
2009-11-30 17:09 ` javier Martin
2009-12-01 15:49 ` Sascha Hauer
2009-12-18 14:18 ` javier Martin
2010-01-08 16:18 ` [alsa-devel] " Mark Brown
2009-11-26 15:53 ` [alsa-devel] [PATCH V2] Add i.MX sound support javier Martin
2009-11-26 16:05 ` Mark Brown
2009-11-27 7:58 ` Sascha Hauer
2009-11-27 9:01 ` javier Martin
2009-11-27 9:54 ` Sascha Hauer
2009-11-30 10:43 ` javier Martin
2009-11-30 12:43 ` Sascha Hauer
2009-11-30 13:13 ` javier Martin
2009-11-30 13:19 ` Sascha Hauer
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=1259163666-30344-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).