alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] ASoC: dapm - fix prefix for DAPM muxes
Date: Tue, 24 May 2011 20:40:51 +0100	[thread overview]
Message-ID: <4DDC09C3.9030609@ti.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0498A482A3@HQMAIL01.nvidia.com>

On 24/05/11 20:37, Stephen Warren wrote:
> Jarkko Nikula wrote at Tuesday, May 24, 2011 12:45 PM:
>> On Tue, 24 May 2011 17:39:09 +0100 Liam Girdwood <lrg@ti.com> wrote:
>>> Make sure DAPM muxes have a valid kcontrol name instead of NULL.
>>>
>>> Signed-off-by: Liam Girdwood <lrg@ti.com>
>>> ---
>>>  sound/soc/soc-dapm.c |    4 ++--
>>>  1 files changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/sound/soc/soc-dapm.c b/sound/soc/soc-dapm.c
>>> index 456617e..c5d98e3 100644
>>> --- a/sound/soc/soc-dapm.c
>>> +++ b/sound/soc/soc-dapm.c
>>> @@ -489,10 +489,10 @@ static int dapm_new_mux(struct snd_soc_dapm_context *dapm,
>>>  	wlist->widgets[wlistentries - 1] = w;
>>>
>>>  	if (!kcontrol) {
>>> -		if (dapm->codec)
>>> +		if (dapm->codec && dapm->codec->name_prefix)
>>>  			prefix = dapm->codec->name_prefix;
>>>  		else
>>> -			prefix = NULL;
>>> +			prefix = w->name;
>>>
>> This didn't look correct to play with prefix. A quick look revealed
>> that there is indeed breakage from commit af46800 ("ASoC: Implement mux
>> control sharing") and this fix doesn't fix it on rx51.
>>
>> I think the breakage must come from dapm_is_shared_kcontrol() that
>> returns always 1 and dapm_new_mux() ends up using w->kcontrol_news
>> [0].name instead of previous w->name.
>>
>> dapm_is_shared_kcontrol() returns always 1 since it gets
>> &w->kcontrol_news[0] as an argument and &w->kcontrol_news[i] will
>> match when iterating the same widget with i==0.
>>
>> 	list_for_each_entry(w, &dapm->card->widgets, list) {
>> 		for (i = 0; i < w->num_kcontrols; i++) {
>> 			if (&w->kcontrol_news[i] == kcontrol_new) {
>> 				if (w->kcontrols)
>> 					*kcontrol = w->kcontrols[i];
>> 				return 1;
>> 			}
>> 		}
>> 	}
>>
>> It works rx51 if I start the iteration from i==1 but it looks the
>> actual fix is to the check that we are not iterating the same widget.
> 
> Yes, I think just add a "struct snd_soc_dapm_widget *kcontrolw" parameter
> to dapm_is_shared_kcontrol(), and make the list_for_each continue if
> w == kcontrolw.
> 
> Sorry, I didn't test this on a system with control name prefixes.
> 
> I can whip up the patch if you want, but won't be able to test that
> it fixes your problems, since none of my systems have prefixes.
> Let me know either way.
> 

Please do. I'll give it a test tomorrow.

Thanks !

Liam

      reply	other threads:[~2011-05-24 19:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 16:39 [PATCH] ASoC: dapm - fix prefix for DAPM muxes Liam Girdwood
2011-05-24 18:45 ` Jarkko Nikula
2011-05-24 19:37   ` Stephen Warren
2011-05-24 19:40     ` Liam Girdwood [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=4DDC09C3.9030609@ti.com \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=swarren@nvidia.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 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).