From: Daniel Mack <zonque@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org,
Sven Neumann <s.neumann@raumfeld.com>,
timur@freescale.com, lrg@ti.com
Subject: Re: [PATCH] ALSA: ASoC: cs4720: use snd_soc_cache_sync()
Date: Tue, 22 Nov 2011 16:23:05 +0100 [thread overview]
Message-ID: <4ECBBE59.2040703@gmail.com> (raw)
In-Reply-To: <20111122140210.GD6624@sirena.org.uk>
On 11/22/2011 03:02 PM, Mark Brown wrote:
> On Tue, Nov 22, 2011 at 02:45:16PM +0100, Daniel Mack wrote:
>> Replace the manual register restore mechanism in cs4270.c and call
>> snd_soc_cache_sync() instead. The current is also wrong, as it doesn't
>> update the internal cache, leading to cache inconsitency after suspend.
>
> I don't understand why this is a bug fix - the code is writing the
> values from the internal cache to the hardware and what's there doesn't
> look obviously wrong...
Hmm, you're right, that isn't obvious. I was too fast in blaming the
code wrong as it stands. But as a matter of fact, the patch *does* fix
the problem, Sven successfully tested it on various devices.
The bug is reproducible by setting the output volume to 50% before
sending the device to suspend. After wakeup, amixer still reports the
old volume level, but the codec is in fact set to 100%. Changing it to
50% doesn't do anything, but to any other level has an effect. This is
clearly a cache sync bug, but the piece that's missing is the reason why
my patch does the right thing.
I'll look into this again - thanks for the heads-up.
next prev parent reply other threads:[~2011-11-22 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 13:45 [PATCH] ALSA: ASoC: cs4720: use snd_soc_cache_sync() Daniel Mack
2011-11-22 14:02 ` Mark Brown
2011-11-22 15:23 ` Daniel Mack [this message]
2011-11-22 15:35 ` Mark Brown
2011-11-22 15:37 ` Timur Tabi
2011-11-22 15:41 ` Daniel Mack
2011-11-22 15:43 ` Mark Brown
2011-11-22 15:44 ` Daniel Mack
2011-11-22 15:47 ` Timur Tabi
2011-11-22 15:57 ` Daniel Mack
2011-11-22 16:12 ` Timur Tabi
2011-11-22 15:53 ` Mark Brown
2011-11-22 16:04 ` Daniel Mack
2011-11-22 16:08 ` 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=4ECBBE59.2040703@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=s.neumann@raumfeld.com \
--cc=timur@freescale.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