Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Ryan Mallon <ryan@bluewatersys.com>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [RFC 12/15] ASoC: multi-component - Cirrus Logic ep93xx Platform
Date: Thu, 01 Jul 2010 07:52:45 +0100	[thread overview]
Message-ID: <1277967165.12813.90.camel@vega> (raw)
In-Reply-To: <4C27C4CF.3010801@bluewatersys.com>

On Mon, 2010-06-28 at 09:38 +1200, Ryan Mallon wrote:
> On 06/27/2010 11:52 PM, Liam Girdwood wrote:
> > Update the Cirrus Logic EP93xx platform and machines to new multi-component model.
> > 
> > This patch changes the machine drivers for multi-component as follows :-
> > 
> >  o Removed socdev
> >  o Each DAI link entry now contains platform and codec fields.
> >  o DAI link init() now passed snd_soc_pcm_runtime instread of snd_soc_codec.
> > 
> > This patch also changes the DAI and platform DAM drivers as follows :-
> > 
> >  o Each platform DAI and platform DMA driver is a kernel device and can
> >    have platform data.
> >  o DAI and Platform DMA drivers have private data accessors.
> > 
> > Other notable changes required for multi-component support:-
> > 
> >  o Add platform devices for I2S and PCM.
> > 
> > Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
> > Signed-off-by: Ryan Mallon <ryan@bluewatersys.com>
> 
> Hi Liam,
> 
> Where does this patch apply to? The codec-id fix, along with the patch I
> just posted for fixing the tlv320aic23 codec, gets the ep93xx/Snapper
> CL15 audio working under on your multi-component branch, so this patch
> should be fine. Would like to test though.

They should apply to 2.6.35-rc1 atm.

Thanks

Liam

  reply	other threads:[~2010-07-01  6:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27 11:51 [RFC 00/15] ASoC: multi-component - Platform Drivers Liam Girdwood
2010-06-27 11:52 ` [RFC 01/15] ASoC: multi-component - Samsung S3C Platform Liam Girdwood
2010-06-27 11:52 ` [RFC 02/15] ASoC: multi-component - TI OMAP Platform Liam Girdwood
2010-06-27 11:52 ` [RFC 03/15] ASoC: multi-component - Atmel Platform Liam Girdwood
2010-06-27 11:52 ` [RFC 04/15] ASoC: multi-component - TI DaVinci Platform Liam Girdwood
2010-06-30 19:28   ` Bedia, Vaibhav
2010-06-27 11:52 ` [RFC 05/15] ASoC: multi-component - Freescale i.MX Platform Liam Girdwood
2010-06-27 11:52 ` [RFC 06/15] ASoC: multi-component - Toshiba Txx9 Platform Liam Girdwood
2010-06-27 11:52 ` [RFC 07/15] ASoC: multi-component - Renasas SuperH Platform Liam Girdwood
2010-06-27 11:52 ` [RFC 08/15] ASoC: multi-component - S6000 Platform Liam Girdwood
2010-06-27 11:52 ` [RFC 09/15] ASoC: multi-component - Freescale PPC Platform Liam Girdwood
2010-06-27 11:52 ` [RFC 10/15] ASoC: multi-component - RMI Alchemy AU1x Platform Liam Girdwood
2010-06-29 12:30   ` Manuel Lauss
2010-06-30  6:40     ` Liam Girdwood
2010-06-27 11:52 ` [RFC 11/15] ASoC: multi-component - Analog Devices Blackfin Platform Liam Girdwood
2010-06-27 11:52 ` [RFC 12/15] ASoC: multi-component - Cirrus Logic ep93xx Platform Liam Girdwood
2010-06-27 21:38   ` Ryan Mallon
2010-07-01  6:52     ` Liam Girdwood [this message]
2010-06-27 11:52 ` [RFC 13/15] ASoC: multi-component - Marvell Kirkwood Platform Liam Girdwood
2010-06-27 11:52 ` [RFC 14/15] ASoC: multi-component - Winbond/Nuvoton NUC900 Platform Liam Girdwood
2010-06-27 11:52 ` [RFC 15/15] ASoC: multi-component - Ingenic J4740 Platform Liam Girdwood
2010-06-27 19:33   ` [PATCH] ASoC: multi-component - JZ4740: Fix issues of the i2s driver in the multi-component branch Lars-Peter Clausen
2010-07-01  6:46     ` 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=1277967165.12813.90.camel@vega \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=ryan@bluewatersys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox