From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] EP93xx: Add i2s core support
Date: Wed, 09 Jun 2010 11:32:13 +1200 [thread overview]
Message-ID: <4C0ED2FD.8090402@bluewatersys.com> (raw)
In-Reply-To: <079055B9-F238-400E-A94D-4B950A5C8C7B@opensource.wolfsonmicro.com>
Mark Brown wrote:
> On 9 Jun 2010, at 00:26, Ryan Mallon wrote:
>
>> Patch 3 at least has a dependency on patch 1 for some #defines and the
>> ep93xx_i2s functions calls.
>
> Oh, in that case best if I take them both through ASoC unless someone anticipates issues there. I'll arrange things so they can also be merged into the ARM tree in case of issues.
Ok, thanks.
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan at bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
next prev parent reply other threads:[~2010-06-08 23:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 10:01 [PATCH 0/3] EP93xx: Add i2s audio support Ryan Mallon
2010-06-08 10:01 ` [PATCH 1/3] EP93xx: Add i2s core support Ryan Mallon
2010-06-08 15:01 ` H Hartley Sweeten
2010-06-08 19:27 ` Ryan Mallon
2010-06-08 23:21 ` Mark Brown
2010-06-08 23:26 ` Ryan Mallon
2010-06-08 23:29 ` Mark Brown
2010-06-08 23:32 ` Ryan Mallon [this message]
2010-06-08 23:26 ` H Hartley Sweeten
2010-06-08 10:01 ` [PATCH 2/3] EP93xx: Add i2s audio driver Ryan Mallon
2010-06-08 10:05 ` Mark Brown
2010-06-08 10:09 ` [alsa-devel] " Ryan Mallon
2010-06-08 10:24 ` Mark Brown
2010-06-08 10:01 ` [PATCH 3/3] EP93xx: Add Snapper CL15 i2s audio support Ryan Mallon
2010-06-09 10:17 ` [PATCH 0/3] EP93xx: Add " Mark Brown
2010-06-09 21:40 ` Ryan Mallon
2010-06-09 22:22 ` Mark Brown
2010-06-10 20:46 ` Ryan Mallon
2010-06-11 9:35 ` [alsa-devel] " 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=4C0ED2FD.8090402@bluewatersys.com \
--to=ryan@bluewatersys.com \
--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).