From: Manuel Lauss <mano@roarinelk.homelinux.net>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Manuel Lauss <mano@roarinelk.homelinux.net>
Subject: Re: [PATCH 09/14] ASoC: multi-component - RMI Alchemy AU1x Platform
Date: Wed, 11 Aug 2010 20:34:20 +0200 [thread overview]
Message-ID: <20100811183420.GA29413@wormhole> (raw)
In-Reply-To: <1281516393-6060-10-git-send-email-lrg@slimlogic.co.uk>
On Wed, Aug 11, 2010 at 09:46:28AM +0100, Liam Girdwood wrote:
> Update the RMI Alchemy 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 Removed empty remove() functions
>
> CC: Manuel Lauss <mano@roarinelk.homelinux.net>
> Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
> @@ -80,8 +75,10 @@ static struct snd_soc_ops db1200_i2s_wm8731_ops = {
> static struct snd_soc_dai_link db1200_i2s_dai = {
> .name = "WM8731",
> .stream_name = "WM8731 PCM",
> - .cpu_dai = &au1xpsc_i2s_dai,
> - .codec_dai = &wm8731_dai,
> + .cpu_dai_name = &au1xpsc_i2s_dai,
> + .codec_dai_name = &wm8731_dai,
> + .platform_name = &au1xpsc_soc_platform,
> + .codec_name = &soc_codec_dev_wm8731,
That doesn't compile, however I have no idea what to set it to.
Is there documentation how component matching is done?
Manuel
next prev parent reply other threads:[~2010-08-11 18:34 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
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 [this message]
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=20100811183420.GA29413@wormhole \
--to=mano@roarinelk.homelinux.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
/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