public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com,
	lrg@ti.com
Subject: Re: [PATCH] ASoC: Fix dapm_is_shared_kcontrol so everything isn't shared
Date: Wed, 25 May 2011 10:01:55 +0300	[thread overview]
Message-ID: <20110525100155.04c8b5e1.jhnikula@gmail.com> (raw)
In-Reply-To: <1306278721-32742-1-git-send-email-swarren@nvidia.com>

On Tue, 24 May 2011 17:12:01 -0600
Stephen Warren <swarren@nvidia.com> wrote:

> Commit af46800 ("ASoC: Implement mux control sharing") introduced
> function dapm_is_shared_kcontrol.
> 
> When this function returns true, the naming of DAPM controls is derived
> from the kcontrol_new. Otherwise, the name comes from the widget (and
> possibly a widget's naming prefix).
> 
> A bug in the implementation of dapm_is_shared_kcontrol made it return 1
> in all cases. Hence, that commit caused a change in control naming for
> all controls instead of just shared controls.
> 
> Specifically, a control is always considered shared because it is always
> compared against itself. Solve this by never comparing against the widget
> containing the control being created.
> 
> I tested that with the Tegra WM8903 driver:
> * Shared is now mostly 0 as expected, and sometimes 1.
> * The expected controls are still generated after this change.
> 
> Howwever, I don't have any systems that have a widget/control naming
> prefix, so I can't test that aspect.
> 
> Reported-by: Liam Girdwood <lrg@ti.com>
> Root-caused-by: Jarkko Nikula <jhnikula@gmail.com>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
>  sound/soc/soc-dapm.c |    5 ++++-
>  1 files changed, 4 insertions(+), 1 deletions(-)
> 
> diff --git a/sound/soc/soc-dapm.c b/sound/soc/soc-dapm.c
> index 456617e..5397699 100644
> --- a/sound/soc/soc-dapm.c
> +++ b/sound/soc/soc-dapm.c
> @@ -325,6 +325,7 @@ static int dapm_connect_mixer(struct snd_soc_dapm_context *dapm,
>  }
>  
>  static int dapm_is_shared_kcontrol(struct snd_soc_dapm_context *dapm,
> +	struct snd_soc_dapm_widget *kcontrolw,
>  	const struct snd_kcontrol_new *kcontrol_new,
>  	struct snd_kcontrol **kcontrol)
>  {
> @@ -334,6 +335,8 @@ static int dapm_is_shared_kcontrol(struct snd_soc_dapm_context *dapm,
>  	*kcontrol = NULL;
>  
>  	list_for_each_entry(w, &dapm->card->widgets, list) {
> +		if (w == kcontrolw)
> +			continue;

Hmm.. it seems this test is not enough with tlv320aic3x.c. It still
classifies a lot of kcontrols to be shared. Will keep hunting.

-- 
Jarkko

  reply	other threads:[~2011-05-25  7:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 23:12 [PATCH] ASoC: Fix dapm_is_shared_kcontrol so everything isn't shared Stephen Warren
2011-05-25  7:01 ` Jarkko Nikula [this message]
2011-05-25 14:52   ` Jarkko Nikula
2011-05-25 15:24     ` Stephen Warren
2011-05-26  6:57       ` Jarkko Nikula
2011-05-26 15:38         ` Stephen Warren
  -- strict thread matches above, loose matches on Subject: below --
2011-05-26 15:57 Stephen Warren
2011-05-26 18:02 ` Jarkko Nikula
2011-05-27  9:19 ` Liam Girdwood
2011-05-27 13:59 ` Mark Brown

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=20110525100155.04c8b5e1.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.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