From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: issue with AD1989A HDA codec and alsamixer
Date: Wed, 2 Feb 2011 08:15:03 +0800 [thread overview]
Message-ID: <AANLkTinec0di98dMdyNoANXBoLG_uRJ+NghEyboCuMUa@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin8tsrNrcoYaPvQz0uO=OtD-tow1Ds0i8WTJyh7@mail.gmail.com>
2011/2/1 Vincent Meserette <vmeserette@aldebaran-robotics.com>
> Hi all,
>
> I am working on a system which includes a connexant AD1989A HDA codec
> connected to a ATOM processor.
> I have four microphones connected to the B and C ports of this codec.
> If I change one of the 3 capture gains present in the alsamixer
> (Capture, Capture 1 or Capture 3), I can't have any more signal on the
> B and C ports
> It seems to be due to the fact that ALSA breaks (for example for the
> Capture gain) the link between the ADC selector 0 and ADC_0 widgets of
> the codec, what can be easily seen with codecgraph.
>
> Have you ever had this kind of problem?
> Do you know how can I resolve it ?
>
> Many thanks for your asnwers and best regards
>
> Vincent
>
What is the Vendor Id of conexant AD1989A ?
are your codec are using patch_analog.c according to vendor id of the codec
?
Looking at the datasheet of ad1988a , ad1988b and ad1989b at analog device
web site and ad1989a conexant web site
The digital microphone of conexant ad1989a only connect to adc0 in the
functional block diagram
next prev parent reply other threads:[~2011-02-02 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 14:57 issue with AD1989A HDA codec and alsamixer Vincent Meserette
2011-02-02 0:15 ` Raymond Yau [this message]
2011-02-02 6:16 ` Raymond Yau
2011-02-02 19:22 ` Vincent Meserette
2011-02-05 9:46 ` Raymond Yau
[not found] ` <AANLkTikugTHmj5aKZqXSi3g50gkqLDXiWmTshBbd9TGQ@mail.gmail.com>
2011-02-07 16:12 ` Raymond Yau
2011-02-08 9:18 ` Raymond Yau
2011-03-23 6:51 ` Raymond Yau
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=AANLkTinec0di98dMdyNoANXBoLG_uRJ+NghEyboCuMUa@mail.gmail.com \
--to=superquad.vortex2@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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).