All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: dp@opensource.wolfsonmicro.com,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Strange control interactions on Tegra Harmony
Date: Thu, 27 Jan 2011 18:49:28 +0000	[thread overview]
Message-ID: <20110127184927.GC12717@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0310C8DD47@HQMAIL01.nvidia.com>

On Thu, Jan 27, 2011 at 10:20:22AM -0800, Stephen Warren wrote:

> The Right Speaker Right Bypass control works the first and all subsequent
> times. Perhaps that's something to do with it being the last entry in
> wm8903.c's right_speaker_mixer[] array?

Possibly, though given the way DAPM processes those arrays I'd be a bit
surprised if it made a difference.  More likely to be that the bypass
paths is one of the simpler and more direct paths in the CODEC.

> I briefly started to debug this, and notice that the SND_SOC_DAPM_SPK event
> function isn't being called at all in the cases where muting doesn't toggle
> as expected.

I noticed something similar while developing a new driver the other day
but didn't get a chance to chase it down yet.  It's likely something got
confused, possibly with the recent changes to propagate DAPM state
between contexts, but that's just a guess as it's the most invasive
thing that happened there recently.

> Can you comment on this? I can certainly continue to debug it, but I figured
> it might be immediately obvious to you what the problem was e.g. if the same
> thing had happened on other platforms/codecs.

I'm on holiday tomorrow so can't have a proper look at live systems - if
you've not got anywhere by Monday I should be able to sort it then.

  reply	other threads:[~2011-01-27 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 18:20 Strange control interactions on Tegra Harmony Stephen Warren
2011-01-27 18:49 ` Mark Brown [this message]
2011-01-27 22:00   ` Stephen Warren
2011-01-27 22:55     ` Stephen Warren
2011-01-28 12:55       ` 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=20110127184927.GC12717@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dp@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 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.