From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH] ASoC: sh: fsi-ak4642: Add FSI port and ak464x selection
Date: Tue, 30 Nov 2010 11:31:38 +0000 [thread overview]
Message-ID: <1291116698.3293.13.camel@odin> (raw)
In-Reply-To: <w3p7hfvbkyl.wl%kuninori.morimoto.gx@renesas.com>
On Tue, 2010-11-30 at 11:32 +0900, Kuninori Morimoto wrote:
> Current FSI-Ak4642 device had niche settings which were
> FSI2-A-AK4643 and FSI-A-AK4642.
> This patch add platform_device_id which can control
> FSI/FSI2, PortA/PortB, AK4642/AK4643 from platform data.
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
but
> static struct snd_soc_dai_link fsi_dai_link = {
> - .name = "AK4642",
> - .stream_name = "AK4642",
> - .cpu_dai_name = "fsia-dai", /* fsi A */
> + /* .name */
> + /* .stream_name */
> + /* .cpu_dai_name */
it looks like you forgot to delete these comments.
> .codec_dai_name = "ak4642-hifi",
> -#ifdef CONFIG_MACH_AP4EVB
> - .platform_name = "sh_fsi2",
> - .codec_name = "ak4642-codec.0-0013",
> -#else
> - .platform_name = "sh_fsi.0",
> - .codec_name = "ak4642-codec.0-0012",
> -#endif
> + /* .platform_name */
> + /* .codec_name */
ditto.
> .init = fsi_ak4642_dai_init,
> .ops = NULL,
no need to set ops to NULL here.
> };
> @@ -50,14 +52,30 @@ static struct snd_soc_card fsi_soc_card = {
>
Could you send an incremental update that fixes these issues.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-11-30 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 2:32 [PATCH] ASoC: sh: fsi-ak4642: Add FSI port and ak464x selection Kuninori Morimoto
2010-11-30 5:56 ` Paul Mundt
2010-11-30 11:31 ` Liam Girdwood [this message]
2010-11-30 11:35 ` 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=1291116698.3293.13.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lethal@linux-sh.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 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.