From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Zhang JieJing <kzjeef@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: WM8993: amp control, amplifying pops.
Date: Mon, 10 May 2010 11:24:23 +0100 [thread overview]
Message-ID: <20100510102422.GD31804@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <v2jcf7b913c1005091910hf7b32843sc71b09b801b8649e@mail.gmail.com>
On Mon, May 10, 2010 at 10:10:53AM +0800, Zhang JieJing wrote:
> I have a question about WM8993 codec's amplifying pops control.
Could you please be more specific about what you mean when you say
"amplifying pops control"? What exactly is an "amplifying pop" (do you
mean that you hear an unwanted noise, or is there something else)?
Please ensure that you are using the latest version of the WM8993 driver
(including wm_hubs.c) to make sure that you have all the latest bug
fixes and enhancements. If you are not using single ended line outputs
from the device you should also mark the line outputs as being in
differential mode for maximum power savings.
> Our board using a WM8993 codec, and I We have problem about ampifying pops,
> when the system resume, We will heard a ampifying pop, (but it's silence on
> the suspend processing), We also noticed that when system boot, also can
> hear one ampifying pop.
System resume and power up are identical from the point of view of the
CODEC driver.
> From I know, the WM8993's codec have a internal amplifier, I don't know how
> to control this amplifier.
The WM8993 has a large number of amplifiers, there are many audio paths
in the device and most of them have some amplification control. Which
outputs are you concerned about?
next parent reply other threads:[~2010-05-10 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v2jcf7b913c1005091910hf7b32843sc71b09b801b8649e@mail.gmail.com>
2010-05-10 10:24 ` Mark Brown [this message]
[not found] ` <AANLkTilrdLPRHI5_4K1C0NHDtonJQzelc6CwW97vuboM@mail.gmail.com>
2010-05-11 11:12 ` WM8993: amp control, amplifying pops 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=20100510102422.GD31804@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=kzjeef@gmail.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;
as well as URLs for NNTP newsgroup(s).