From: Lars-Peter Clausen <lars@metafoo.de>
To: Bo Shen <voice.shen@atmel.com>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
linux-sound@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: wm8904: fix runtime warning
Date: Mon, 12 Jan 2015 10:30:36 +0100 [thread overview]
Message-ID: <54B3943C.4040103@metafoo.de> (raw)
In-Reply-To: <54B34035.60107@atmel.com>
On 01/12/2015 04:32 AM, Bo Shen wrote:
[...]
>>> diff --git a/sound/soc/codecs/wm8904.c b/sound/soc/codecs/wm8904.c
>>> index 4d2d2b1..38582d7 100644
>>> --- a/sound/soc/codecs/wm8904.c
>>> +++ b/sound/soc/codecs/wm8904.c
>>> @@ -1076,10 +1076,10 @@ static const struct snd_soc_dapm_route
>>> adc_intercon[] = {
>>> { "Right Capture PGA", NULL, "Right Capture Mux" },
>>> { "Right Capture PGA", NULL, "Right Capture Inverting Mux" },
>>>
>>> - { "AIFOUTL", "Left", "ADCL" },
>>> - { "AIFOUTL", "Right", "ADCR" },
>>> - { "AIFOUTR", "Left", "ADCL" },
>>> - { "AIFOUTR", "Right", "ADCR" },
>>> + { "AIFOUTL", NULL, "ADCL" },
>>> + { "AIFOUTL", NULL, "ADCR" },
>>> + { "AIFOUTR", NULL, "ADCL" },
>>> + { "AIFOUTR", NULL, "ADCR" },
>>
>> Is this the right fix here? I am not super familiar with the
>> driver but it appears to contain an "AIFOUTL Mux" control which
>> is not connected to anything. Looks like maybe this is a mistake
>> the mux is indeded to be included in the path? Feels like we
>> should either remove the control as well or hook it into the
>> path.
>
> Thank for your information.
> I think here it should correct the path name as
> --->8---
> { "AIFOUTL Mux", "Left", "ADCL" },
> { "AIFOUTL Mux", "Right", "ADCR" },
> { "AIFOUTR Mux", "Left", "ADCL" },
> { "AIFOUTR Mux", "Right", "ADCR" },
> ---8<---
>
> Thanks again. I will send out the new version.
Your probably also need to connect the mux to the output pins.
WARNING: multiple messages have this Message-ID (diff)
From: Lars-Peter Clausen <lars@metafoo.de>
To: Bo Shen <voice.shen@atmel.com>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
linux-sound@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: wm8904: fix runtime warning
Date: Mon, 12 Jan 2015 09:30:36 +0000 [thread overview]
Message-ID: <54B3943C.4040103@metafoo.de> (raw)
In-Reply-To: <54B34035.60107@atmel.com>
On 01/12/2015 04:32 AM, Bo Shen wrote:
[...]
>>> diff --git a/sound/soc/codecs/wm8904.c b/sound/soc/codecs/wm8904.c
>>> index 4d2d2b1..38582d7 100644
>>> --- a/sound/soc/codecs/wm8904.c
>>> +++ b/sound/soc/codecs/wm8904.c
>>> @@ -1076,10 +1076,10 @@ static const struct snd_soc_dapm_route
>>> adc_intercon[] = {
>>> { "Right Capture PGA", NULL, "Right Capture Mux" },
>>> { "Right Capture PGA", NULL, "Right Capture Inverting Mux" },
>>>
>>> - { "AIFOUTL", "Left", "ADCL" },
>>> - { "AIFOUTL", "Right", "ADCR" },
>>> - { "AIFOUTR", "Left", "ADCL" },
>>> - { "AIFOUTR", "Right", "ADCR" },
>>> + { "AIFOUTL", NULL, "ADCL" },
>>> + { "AIFOUTL", NULL, "ADCR" },
>>> + { "AIFOUTR", NULL, "ADCL" },
>>> + { "AIFOUTR", NULL, "ADCR" },
>>
>> Is this the right fix here? I am not super familiar with the
>> driver but it appears to contain an "AIFOUTL Mux" control which
>> is not connected to anything. Looks like maybe this is a mistake
>> the mux is indeded to be included in the path? Feels like we
>> should either remove the control as well or hook it into the
>> path.
>
> Thank for your information.
> I think here it should correct the path name as
> --->8---
> { "AIFOUTL Mux", "Left", "ADCL" },
> { "AIFOUTL Mux", "Right", "ADCR" },
> { "AIFOUTR Mux", "Left", "ADCL" },
> { "AIFOUTR Mux", "Right", "ADCR" },
> ---8<---
>
> Thanks again. I will send out the new version.
Your probably also need to connect the mux to the output pins.
WARNING: multiple messages have this Message-ID (diff)
From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH] ASoC: wm8904: fix runtime warning
Date: Mon, 12 Jan 2015 10:30:36 +0100 [thread overview]
Message-ID: <54B3943C.4040103@metafoo.de> (raw)
In-Reply-To: <54B34035.60107@atmel.com>
On 01/12/2015 04:32 AM, Bo Shen wrote:
[...]
>>> diff --git a/sound/soc/codecs/wm8904.c b/sound/soc/codecs/wm8904.c
>>> index 4d2d2b1..38582d7 100644
>>> --- a/sound/soc/codecs/wm8904.c
>>> +++ b/sound/soc/codecs/wm8904.c
>>> @@ -1076,10 +1076,10 @@ static const struct snd_soc_dapm_route
>>> adc_intercon[] = {
>>> { "Right Capture PGA", NULL, "Right Capture Mux" },
>>> { "Right Capture PGA", NULL, "Right Capture Inverting Mux" },
>>>
>>> - { "AIFOUTL", "Left", "ADCL" },
>>> - { "AIFOUTL", "Right", "ADCR" },
>>> - { "AIFOUTR", "Left", "ADCL" },
>>> - { "AIFOUTR", "Right", "ADCR" },
>>> + { "AIFOUTL", NULL, "ADCL" },
>>> + { "AIFOUTL", NULL, "ADCR" },
>>> + { "AIFOUTR", NULL, "ADCL" },
>>> + { "AIFOUTR", NULL, "ADCR" },
>>
>> Is this the right fix here? I am not super familiar with the
>> driver but it appears to contain an "AIFOUTL Mux" control which
>> is not connected to anything. Looks like maybe this is a mistake
>> the mux is indeded to be included in the path? Feels like we
>> should either remove the control as well or hook it into the
>> path.
>
> Thank for your information.
> I think here it should correct the path name as
> --->8---
> { "AIFOUTL Mux", "Left", "ADCL" },
> { "AIFOUTL Mux", "Right", "ADCR" },
> { "AIFOUTR Mux", "Left", "ADCL" },
> { "AIFOUTR Mux", "Right", "ADCR" },
> ---8<---
>
> Thanks again. I will send out the new version.
Your probably also need to connect the mux to the output pins.
next prev parent reply other threads:[~2015-01-12 9:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 8:53 [PATCH] ASoC: wm8904: fix runtime warning Bo Shen
2015-01-09 8:53 ` Bo Shen
2015-01-09 8:53 ` Bo Shen
2015-01-09 8:53 ` Bo Shen
2015-01-09 11:16 ` [alsa-devel] " Charles Keepax
2015-01-09 11:16 ` Charles Keepax
2015-01-09 11:16 ` Charles Keepax
2015-01-12 3:32 ` Bo Shen
2015-01-12 3:32 ` Bo Shen
2015-01-12 3:32 ` Bo Shen
2015-01-12 3:32 ` Bo Shen
2015-01-12 9:30 ` Lars-Peter Clausen [this message]
2015-01-12 9:30 ` Lars-Peter Clausen
2015-01-12 9:30 ` Lars-Peter Clausen
2015-01-13 5:36 ` Bo Shen
2015-01-13 5:36 ` Bo Shen
2015-01-13 5:36 ` Bo Shen
2015-01-13 5:36 ` Bo Shen
2015-01-13 8:56 ` Lars-Peter Clausen
2015-01-13 8:56 ` Lars-Peter Clausen
2015-01-13 8:56 ` Lars-Peter Clausen
2015-01-13 9:33 ` Bo Shen
2015-01-13 9:33 ` Bo Shen
2015-01-13 9:33 ` Bo Shen
2015-01-13 9:33 ` Bo Shen
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=54B3943C.4040103@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=voice.shen@atmel.com \
/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.