From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com
Subject: Re: i.MX SDMA support
Date: Mon, 09 Aug 2010 11:47:03 +0100 [thread overview]
Message-ID: <1281350823.3035.54.camel@odin> (raw)
In-Reply-To: <20100809091157.GC20065@pengutronix.de>
On Mon, 2010-08-09 at 11:11 +0200, Sascha Hauer wrote:
> Hi,
>
> I just posted a series adding SDMA support for i.MX to the Arm Linux
> Kernel mailing list.
I noticed. It's good to see SDMA support going upstream :)
> It also contains a patch for adding SDMA support
> to the i.MX SSI units. I haven't cc'd alsa-devel because most of the
> stuff is not sound related. I know at least Mark and Liam are
> interested, so I leave a pointer here. The sound stuff needs to be
> synchronized with the other patches, so it's probably best if all
> patches go via my tree.
Yeah, that should be OK. However, we do have a ASoC core multi-component
update merging later this week. This may conflict with some of your SDMA
updates, although the multi-component support only really affects ASoC
component probe() and remove() as every component is a regular Linux
device now (with platform data, etc) and private data access.
The multi-component branch is here:-
git://git.kernel.org/pub/scm/linux/kernel/git/lrg/asoc-2.6.git topic/multi-component
I did have to make some changes to i.MX ASoC in order to de-couple some
of the components in order for them to be distinct kernel devices. Any
chance you could give this a test with the new SDMA code ?
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-08-09 10:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 9:11 i.MX SDMA support Sascha Hauer
2010-08-09 10:47 ` Liam Girdwood [this message]
2010-08-09 12:19 ` Sascha Hauer
2010-08-09 14:09 ` Mark Brown
2010-08-10 13:15 ` Sascha Hauer
2010-08-10 13:39 ` Mark Brown
2010-08-10 14:07 ` Liam Girdwood
2010-08-11 8:42 ` Sascha Hauer
2010-08-11 10:09 ` Liam Girdwood
2010-08-11 11:59 ` Sascha Hauer
2010-08-11 12:32 ` Liam Girdwood
2010-08-11 13:43 ` Liam Girdwood
2010-08-11 8:44 ` Sascha Hauer
2010-08-11 10:24 ` Liam Girdwood
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=1281350823.3035.54.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=s.hauer@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.