From: Lars-Peter Clausen <lars@metafoo.de>
To: Scott Jiang <scott.jiang.linux@gmail.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
stable@kernel.org, device-drivers-devel@blackfin.uclinux.org,
uclinux-dist-devel@blackfin.uclinux.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: Blackfin: bf5xx-ad193x: Fix codec device name
Date: Tue, 06 Sep 2011 10:16:27 +0200 [thread overview]
Message-ID: <4E65D6DB.7030805@metafoo.de> (raw)
In-Reply-To: <CAHG8p1B9Oshc6GgJn8UyERczGB2E0B=6nB6UsPX5Pis_CxUdmg@mail.gmail.com>
On 09/06/2011 04:35 AM, Scott Jiang wrote:
> 2011/9/5 Lars-Peter Clausen <lars@metafoo.de>:
>> Fix the codec_name field of the dai_link to match the actual device name
>> of the codec. Otherwise the card won't be instantiated.
>>
>> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
>> Cc: stable@kernel.org
>> ---
>> sound/soc/blackfin/bf5xx-ad193x.c | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/sound/soc/blackfin/bf5xx-ad193x.c b/sound/soc/blackfin/bf5xx-ad193x.c
>> index a118a0f..5956584 100644
>> --- a/sound/soc/blackfin/bf5xx-ad193x.c
>> +++ b/sound/soc/blackfin/bf5xx-ad193x.c
>> @@ -103,7 +103,7 @@ static struct snd_soc_dai_link bf5xx_ad193x_dai[] = {
>> .cpu_dai_name = "bfin-tdm.0",
>> .codec_dai_name ="ad193x-hifi",
>> .platform_name = "bfin-tdm-pcm-audio",
>> - .codec_name = "ad193x.5",
>> + .codec_name = "spi0.5",
>> .ops = &bf5xx_ad193x_ops,
>> },
>> {
>> @@ -112,7 +112,7 @@ static struct snd_soc_dai_link bf5xx_ad193x_dai[] = {
>> .cpu_dai_name = "bfin-tdm.1",
>> .codec_dai_name ="ad193x-hifi",
>> .platform_name = "bfin-tdm-pcm-audio",
>> - .codec_name = "ad193x.5",
>> + .codec_name = "spi0.5",
>> .ops = &bf5xx_ad193x_ops,
>> },
>> };
>> --
>> 1.7.2.5
>
> Lars, I have to tell you ad193x supports i2c and spi.
>
> #if defined(CONFIG_SND_SOC_AD193X_SPI)
> .codec_name = "spi0.5",
> #elif defined(CONFIG_SND_SOC_AD193X_I2C)
> .codec_name = "ad193x.0-0004",
> #endif
>
> It is better to modify machine driver to platform driver and pass in
> control type.
>
> Scott
Yes, though I would prefer using platform_device_id for this since whether it
is I2C or SPI depends on the codec model.
- Lars
prev parent reply other threads:[~2011-09-06 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 11:49 [PATCH] ASoC: Blackfin: bf5xx-ad193x: Fix codec device name Lars-Peter Clausen
2011-09-06 0:41 ` Girdwood, Liam
2011-09-06 1:11 ` Mark Brown
2011-09-06 2:35 ` Scott Jiang
2011-09-06 8:16 ` Lars-Peter Clausen [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=4E65D6DB.7030805@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=lrg@ti.com \
--cc=scott.jiang.linux@gmail.com \
--cc=stable@kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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