From: Takashi Iwai <tiwai@suse.de>
To: "Ivan N. Zlatev" <contact@i-nz.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: Strange findings about the microphone in SigmaTel STAC9221 A1
Date: Tue, 15 May 2007 14:26:30 +0200 [thread overview]
Message-ID: <s5hps52gtmx.wl%tiwai@suse.de> (raw)
In-Reply-To: <3db1ec7f0705110248p788b3d9q2ea5774331fded9d@mail.gmail.com>
At Fri, 11 May 2007 10:48:44 +0100,
Ivan N. Zlatev wrote:
>
> My hda-intel card is with the following codec:
>
> Codec: SigmaTel STAC9221 A1
> Address: 0
> Vendor Id: 0x83847680
> Subsystem Id: 0x106b1700
> Revision Id: 0x103401
>
> I am using alsa 1.0.14rc4. I have a built-in microphone, which doesn't
> work, but today I found out something interesting. If I set the
> capture to minimum and place Mux at specific positions (Works with
> middle-ish and top, not bottom-ish) suddenly the mic started
> recording, but the quality is extremly bad. I have attached amixer and
> co. Does anyone have a clue what the issue is and how could possibly
> this little bit of random foundings to be used to possibly fix the
> mic?
If this is 100% reproducible, you'll see likely a difference in
/proc/asound/card0/codec#* file between working and non-working
states. Could you attach codec files in both states?
The quality problem is perhaps because of the wrong pin setting.
It's set in Hi-Z without vref. But it's a bit strange because
stac92xx_get_vref() should return the proper vref value. Could you
check whether this really gets called and which value is returned,
e.g. by adding printk() there?
Takashi
next prev parent reply other threads:[~2007-05-15 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 9:48 Strange findings about the microphone in SigmaTel STAC9221 A1 Ivan N. Zlatev
2007-05-15 12:26 ` Takashi Iwai [this message]
2007-05-15 14:41 ` Ivan N. Zlatev
2007-05-15 15:06 ` Takashi Iwai
2007-05-15 17:11 ` Ivan N. Zlatev
2007-05-15 17:23 ` Ivan N. Zlatev
2007-05-18 17:12 ` Takashi Iwai
2007-05-19 20:28 ` Ivan N. Zlatev
2007-05-19 21:23 ` Ivan N. Zlatev
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=s5hps52gtmx.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=contact@i-nz.net \
/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).