All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
	alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Peter Ujfalusi <peter.ujfalusi@nokia.com>
Subject: Re: [PATCH 01/14] ASoC: multi-component - TI OMAP Platform
Date: Wed, 11 Aug 2010 12:44:28 +0100	[thread overview]
Message-ID: <1281527068.3080.82.camel@odin> (raw)
In-Reply-To: <20100811140418.a802cd94.jhnikula@gmail.com>

On Wed, 2010-08-11 at 14:04 +0300, Jarkko Nikula wrote:
> Hi
> 
> On Wed, 11 Aug 2010 09:46:20 +0100
> Liam Girdwood <lrg@slimlogic.co.uk> wrote:
> 
> > Other notable changes required for multi-component support:-
> > 
> >  o Moved zoom2 audio platform data to board-zoom2.c
> >  o Moved n810 audio platform data to board-n810.c
> >  o Moved RX51 audio platform data to board-rx51-peripherals.c
> >  o Added ASoC DAI and DMA platform devices.
> 
> Here are rejects from these two files when applied to Vanilla:
> 
> arch/arm/mach-omap2/board-rx51-peripherals.c
> arch/arm/mach-omap2/board-zoom2.c
> 
> Fortunately trivial.
> 
> board-rx51-peripherals.c conflicts with rx51_aic3x_data (i.e. add only
> rx51_aic34_setup) and board-zoom2.c with board_nand_init in
> omap_zoom2_init.
> 
> board-n8x0.c will conflict in 2.6.37 with changes from linux-omap but
> this is easiest to handle if you leave out the
> arch/arm/mach-omap2/board-n8x0.c changes. IMO n810_aic33_setup for
> the digital microphone can be patched after m-c.
> 

Thanks, I was expecting some conflicts in arch. Hopefully, these will
lessen when the 2.6.37 merge starts and I can rebase to a more recent
kernel before m-c is merged.

> >  o Misc fixes from Jarkko Nikula
> > 
> Add Peter also as he sent fixes too :-)

Oops.

Thanks

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

  reply	other threads:[~2010-08-11 11:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11  8:46 [PATCH 00/14] ASoC: multi-component platform support Liam Girdwood
2010-08-11  8:46 ` [PATCH 01/14] ASoC: multi-component - TI OMAP Platform Liam Girdwood
2010-08-11 11:04   ` Jarkko Nikula
2010-08-11 11:44     ` Liam Girdwood [this message]
2010-08-11  8:46 ` [PATCH 02/14] ASoC: multi-component - Atmel Platform Liam Girdwood
2010-08-18  9:28   ` Nicolas Ferre
2010-08-11  8:46 ` [PATCH 03/14] ASoC: multi-component - TI DaVinci Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 04/14] ASoC: multi-component - Freescale i.MX Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 05/14] ASoC: multi-component - Toshiba Txx9 Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 06/14] ASoC: multi-component - Renasas SuperH Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 07/14] ASoC: multi-component - S6000 Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 08/14] ASoC: multi-component - Freescale PPC Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 09/14] ASoC: multi-component - RMI Alchemy AU1x Platform Liam Girdwood
2010-08-11 18:34   ` Manuel Lauss
2010-08-11 21:07     ` Liam Girdwood
2010-08-12 13:15       ` Liam Girdwood
2010-08-11  8:46 ` [PATCH 10/14] ASoC: multi-component - Analog Devices Blackfin Platform Liam Girdwood
2010-08-12  3:46   ` Mike Frysinger
2010-08-12  3:47     ` Mike Frysinger
2010-08-12  7:57       ` Liam Girdwood
2010-08-12 11:17         ` Mike Frysinger
2010-08-12 11:30           ` Liam Girdwood
2010-08-12 11:33             ` Liam Girdwood
2010-08-12 11:56               ` Mike Frysinger
2010-08-12 10:34       ` Mark Brown
2010-08-11  8:46 ` [PATCH 11/14] ASoC: multi-component - Cirrus Logic ep93xx Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 12/14] ASoC: multi-component - Marvell Kirkwood Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 13/14] ASoC: multi-component - Winbond/Nuvoton NUC900 Platform Liam Girdwood
2010-08-11  8:46 ` [PATCH 14/14] ASoC: multi-component - Ingenic J4740 Platform 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=1281527068.3080.82.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jhnikula@gmail.com \
    --cc=peter.ujfalusi@nokia.com \
    --cc=tony@atomide.com \
    /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.