From: Jarkko Nikula <jhnikula@gmail.com>
To: "Koyamangalath, Abhilash" <abhilash.kv@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"alsa-devel@vger.kernel.org" <alsa-devel@vger.kernel.org>
Subject: Re: [TLV320AIC23] [AM3517EVM][AUDIO] codec name mis-match in soc_bind_dai_link
Date: Tue, 1 Mar 2011 12:42:43 +0200 [thread overview]
Message-ID: <20110301124243.6c329c74.jhnikula@gmail.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC3560870370776EC3@dbde02.ent.ti.com>
On Tue, 1 Mar 2011 15:22:29 +0530
"Koyamangalath, Abhilash" <abhilash.kv@ti.com> wrote:
> Now, if I change the dai-link->codec_name to force-match by appending 2-001a to the codec_name in (sound/soc/omap/am3517evm.c):
> static struct snd_soc_dai_link am3517evm_dai = {
> :
> .codec_name = "tlv320aic23-codec.2-001a ",
> :
> };
>
> the registration proceeds smoothly and I can see device nodes getting created.
> Since now there is no way to provide a customized i2c device name to a client device (or so I believe), what could be the best solution to this problem ?
>
The fix above. Care to check also osk5912.c?
--
Jarkko
prev parent reply other threads:[~2011-03-01 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 9:52 [TLV320AIC23] [AM3517EVM][AUDIO] codec name mis-match in soc_bind_dai_link Koyamangalath, Abhilash
2011-03-01 10:42 ` Jarkko Nikula [this message]
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=20110301124243.6c329c74.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=abhilash.kv@ti.com \
--cc=alsa-devel@vger.kernel.org \
--cc=linux-omap@vger.kernel.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