All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Mallon <ryan@bluewatersys.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "john.cooper@third-harmonic.com" <john.cooper@third-harmonic.com>,
	"chasedouglas@gmail.com" <chasedouglas@gmail.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"r&d4@dave-tech.it" <r&d4@dave-tech.it>,
	H Hartley Sweeten <hartleys@visionengravers.com>,
	"dhuggins@cs.cmu.edu" <dhuggins@cs.cmu.edu>,
	"marshall@coolbananas.co.nz" <marshall@coolbananas.co.nz>,
	"buytenh@wantstofly.org" <buytenh@wantstofly.org>,
	"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/3] EP93xx: Add i2s core support
Date: Wed, 09 Jun 2010 11:26:49 +1200	[thread overview]
Message-ID: <4C0ED1B9.7020106@bluewatersys.com> (raw)
In-Reply-To: <94CDC52C-12BD-447E-B0ED-5E3950FF89BA@opensource.wolfsonmicro.com>

Mark Brown wrote:
> On 8 Jun 2010, at 20:27, Ryan Mallon wrote:
> 
>> Okay, I have Liam and Hartley's acks on this one and Liam's on 3/3.
>> Mark, do you want to apply the other two patches to your tree, or should
>> they go via the arm tree?
> 
> I don't urgently mind for patch 1 since there's no build time dependency - in order to avoid possible merge issues in the ARM tree it's as well if it goes that way, though I can pick it up if it makes sense for you guys to keep stuff together and you don't anticipate colliding with any work in the arch/arm code for the CPU.
> 
> Patch 3 I'll apply to ASoC tomorrow, it depends on the I2S driver for the CPU which is most definitely ASoC (and it's going to get caught up in the multi-CODEC API changes soon as well so would get build issues in -next if merged via a different tree anyway).
> 

Patch 3 at least has a dependency on patch 1 for some #defines and the
ep93xx_i2s functions calls.

~Ryan

-- 
Bluewater Systems Ltd - ARM Technology Solution Centre

Ryan Mallon         		5 Amuri Park, 404 Barbadoes St
ryan@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

WARNING: multiple messages have this Message-ID (diff)
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:26:49 +1200	[thread overview]
Message-ID: <4C0ED1B9.7020106@bluewatersys.com> (raw)
In-Reply-To: <94CDC52C-12BD-447E-B0ED-5E3950FF89BA@opensource.wolfsonmicro.com>

Mark Brown wrote:
> On 8 Jun 2010, at 20:27, Ryan Mallon wrote:
> 
>> Okay, I have Liam and Hartley's acks on this one and Liam's on 3/3.
>> Mark, do you want to apply the other two patches to your tree, or should
>> they go via the arm tree?
> 
> I don't urgently mind for patch 1 since there's no build time dependency - in order to avoid possible merge issues in the ARM tree it's as well if it goes that way, though I can pick it up if it makes sense for you guys to keep stuff together and you don't anticipate colliding with any work in the arch/arm code for the CPU.
> 
> Patch 3 I'll apply to ASoC tomorrow, it depends on the I2S driver for the CPU which is most definitely ASoC (and it's going to get caught up in the multi-CODEC API changes soon as well so would get build issues in -next if merged via a different tree anyway).
> 

Patch 3 at least has a dependency on patch 1 for some #defines and the
ep93xx_i2s functions calls.

~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

  reply	other threads:[~2010-06-08 23:26 UTC|newest]

Thread overview: 38+ 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 ` Ryan Mallon
2010-06-08 10:01 ` [PATCH 1/3] EP93xx: Add i2s core support Ryan Mallon
2010-06-08 10:01   ` Ryan Mallon
2010-06-08 15:01   ` H Hartley Sweeten
2010-06-08 15:01     ` H Hartley Sweeten
2010-06-08 19:27     ` Ryan Mallon
2010-06-08 19:27       ` Ryan Mallon
2010-06-08 23:21       ` Mark Brown
2010-06-08 23:21         ` Mark Brown
2010-06-08 23:26         ` Ryan Mallon [this message]
2010-06-08 23:26           ` Ryan Mallon
2010-06-08 23:29           ` Mark Brown
2010-06-08 23:29             ` Mark Brown
2010-06-08 23:32             ` Ryan Mallon
2010-06-08 23:32               ` Ryan Mallon
2010-06-08 23:26       ` H Hartley Sweeten
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:01   ` Ryan Mallon
2010-06-08 10:05   ` Mark Brown
2010-06-08 10:05     ` Mark Brown
2010-06-08 10:09     ` Ryan Mallon
2010-06-08 10:09       ` [alsa-devel] " Ryan Mallon
2010-06-08 10:24       ` Mark Brown
2010-06-08 10:24         ` [alsa-devel] " Mark Brown
2010-06-08 10:01 ` [PATCH 3/3] EP93xx: Add Snapper CL15 i2s audio support Ryan Mallon
2010-06-08 10:01   ` Ryan Mallon
2010-06-09 10:17 ` [PATCH 0/3] EP93xx: Add " Mark Brown
2010-06-09 10:17   ` Mark Brown
2010-06-09 21:40   ` Ryan Mallon
2010-06-09 21:40     ` Ryan Mallon
2010-06-09 22:22     ` Mark Brown
2010-06-09 22:22       ` Mark Brown
2010-06-10 20:46       ` Ryan Mallon
2010-06-10 20:46         ` Ryan Mallon
2010-06-11  9:35         ` Mark Brown
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=4C0ED1B9.7020106@bluewatersys.com \
    --to=ryan@bluewatersys.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=buytenh@wantstofly.org \
    --cc=chasedouglas@gmail.com \
    --cc=dhuggins@cs.cmu.edu \
    --cc=hartleys@visionengravers.com \
    --cc=john.cooper@third-harmonic.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=marshall@coolbananas.co.nz \
    --cc=r&d4@dave-tech.it \
    /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.