From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Johannes Stezenbach <js@sig21.net>
Cc: alsa-devel@alsa-project.org,
Sven Neumann <s.neumann@raumfeld.com>, Liam Girdwood <lrg@ti.com>,
Daniel Mack <daniel@zonque.org>
Subject: Re: [PATCH] ASoC: sta32x: add workaround for ESD reset issue
Date: Thu, 10 Nov 2011 15:11:37 +0000 [thread overview]
Message-ID: <20111110151136.GH3832@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111110142708.GA12808@sig21.net>
On Thu, Nov 10, 2011 at 03:27:08PM +0100, Johannes Stezenbach wrote:
> On Wed, Nov 09, 2011 at 11:32:57PM +0000, Mark Brown wrote:
> > Yeah, but if it suddenly stops in the middle of playback then that'll
> > tend to register with users and if you keep it powered off at all other
> > times.
> Hm, the goal is to fix the issue without user interaction.
> The app will keep the device open and will play back
> without noticing the problem.
Well, the user is going to hear a horrific glitch anyway...
> > Right, but the bias level management is disabling the regulators for the
> > device so power loss may happen then and _STANDBY is also used to resume
> > the device after suspend when power loss may also occur.
> Ah, you're right, if the system cuts power to the sta32x during
> standby we need to restore the coef RAM after resume. How I
> see where my code is buggy. I also see what you mean about
> using idle_bias_off to restore the settings, namely
> level = codec->dapm.bias_level;
> BUG_ON(level == SND_SOC_BIAS_OFF);
> sta32x_set_bias_level(codec, SND_SOC_BIAS_OFF);
> sta32x_set_bias_level(codec, SND_SOC_BIAS_STANDBY);
> if (level > SND_SOC_BIAS_STANDBY);
> sta32x_set_bias_level(codec, SND_SOC_BIAS_PREPARE);
> if (level > SND_SOC_BIAS_PREPARE);
> sta32x_set_bias_level(codec, SND_SOC_BIAS_ON);
> Right?
Not really what I meant - I meant just let the framework power the
device down when it goes idle so you don't have to worry about it
resetting - though you will need to go through the
OFF->STANDBY->PREPARE->ON transition to bring the device up nicely if
you do restart while active.
next prev parent reply other threads:[~2011-11-10 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 13:30 [PATCH] ASoC: sta32x: add workaround for ESD reset issue Johannes Stezenbach
2011-11-09 14:36 ` Mark Brown
2011-11-09 17:34 ` Johannes Stezenbach
2011-11-09 23:32 ` Mark Brown
2011-11-10 14:27 ` Johannes Stezenbach
2011-11-10 15:11 ` Mark Brown [this message]
2011-11-10 16:49 ` Sven Neumann
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=20111110151136.GH3832@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=daniel@zonque.org \
--cc=js@sig21.net \
--cc=lrg@ti.com \
--cc=s.neumann@raumfeld.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.