All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: bardliao@realtek.com
Cc: oder_chiou@realtek.com, alsa-devel@alsa-project.org,
	swarren@nvidia.com, lgirdwood@gmail.com, broonie@kernel.org,
	flove@realtek.com
Subject: Re: [PATCH] ASoC: rt5640: change widget sequence for depop
Date: Mon, 19 Aug 2013 11:29:32 -0600	[thread overview]
Message-ID: <521255FC.4000003@wwwdotorg.org> (raw)
In-Reply-To: <1376914682-3606-1-git-send-email-bardliao@realtek.com>

On 08/19/2013 06:18 AM, bardliao@realtek.com wrote:
> From: Bard Liao <bardliao@realtek.com>
> 
> Add mute/unmute control in widget event and modify the power on/off sequence to avoid pop noise.

This version breaks both headphone and speaker output. I see the
following issues:

1)

After a reboot, if all of "{HP,Speaker} [LR] Playback Switch" are
on/unmuted, and I start playback, then something sets all those controls
to off/muted. I suspect this is related to function rt5640_hp_event()
twiddling the same RT5640_[LR]_MUTE bits that the hp_[lr]_enable_control
controls twiddle.

2)

If playback is running, and (1) has caused all output to be muted, and I
then run alsamixer and enable/unmute "HP L Playback Switch", I hear
sound on both the L and R headphone channels for a very brief time, then
output switches to the L channel only. Similar happens if I unmute "HP R
Playback Switch" first. Unmuting both switches does produce stereo sound
as expected.

I don't know if this also happens for the speaker output, since the
board is too far away from me to easily tell which speakers are playing.

  reply	other threads:[~2013-08-19 17:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 12:18 [PATCH] ASoC: rt5640: change widget sequence for depop bardliao
2013-08-19 17:29 ` Stephen Warren [this message]
2013-08-20  2:36   ` Bard Liao
2013-08-20 16:15     ` Stephen Warren
2013-08-21 19:56       ` Lars-Peter Clausen
  -- strict thread matches above, loose matches on Subject: below --
2013-08-05  4:19 bardliao
2013-08-05 14:48 ` Mark Brown
2013-08-05 17:21   ` Lars-Peter Clausen
2013-08-05 17:58     ` Mark Brown
2013-08-05 17:17 ` Stephen Warren
2013-08-05 17:19 ` Lars-Peter Clausen
2013-08-02  2:38 bardliao
2013-08-02 15:53 ` Stephen Warren
2013-08-05  3:34   ` Bard Liao

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=521255FC.4000003@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=broonie@kernel.org \
    --cc=flove@realtek.com \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.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.