From: lrg@slimlogic.co.uk (Liam Girdwood)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] davinci: da8xx/omap-l1xx: match codec_name with i2c ids
Date: Fri, 21 Jan 2011 14:38:28 +0000 [thread overview]
Message-ID: <1295620708.3348.233.camel@odin> (raw)
In-Reply-To: <1295619896-5498-1-git-send-email-sudhakar.raj@ti.com>
On Fri, 2011-01-21 at 19:54 +0530, Rajashekhara, Sudhakar wrote:
> The codec_name entry for da8xx evm in sound/soc/davinci/davinci-evm.c
> is not matching with the i2c ids in the board file. Without this fix the
> soundcard does not get detected on da850/omap-l138/am18x evm.
>
> Signed-off-by: Rajashekhara, Sudhakar <sudhakar.raj@ti.com>
> Tested-by: Dan Sharon <dansharon@nanometrics.ca>
> ---
> This patch applies to Linus's kernel tree.
>
> sound/soc/davinci/davinci-evm.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/sound/soc/davinci/davinci-evm.c b/sound/soc/davinci/davinci-evm.c
> index 0c2d6ba..b36f0b3 100644
> --- a/sound/soc/davinci/davinci-evm.c
> +++ b/sound/soc/davinci/davinci-evm.c
> @@ -223,7 +223,7 @@ static struct snd_soc_dai_link da8xx_evm_dai = {
> .stream_name = "AIC3X",
> .cpu_dai_name= "davinci-mcasp.0",
> .codec_dai_name = "tlv320aic3x-hifi",
> - .codec_name = "tlv320aic3x-codec.0-001a",
> + .codec_name = "tlv320aic3x-codec.1-0018",
> .platform_name = "davinci-pcm-audio",
> .init = evm_aic3x_init,
> .ops = &evm_ops,
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2011-01-21 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 14:24 [PATCH] davinci: da8xx/omap-l1xx: match codec_name with i2c ids Rajashekhara, Sudhakar
2011-01-21 14:38 ` Liam Girdwood [this message]
2011-01-24 23:00 ` Kevin Hilman
2011-01-24 23:09 ` Kevin Hilman
2011-01-25 10:59 ` [alsa-devel] " Liam Girdwood
2011-01-25 12:35 ` Mark Brown
2011-01-25 18:36 ` Kevin Hilman
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=1295620708.3348.233.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).