From: David Henningsson <david.henningsson@canonical.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] ALSA: hda - Sort input pins depending on amp caps
Date: Wed, 24 Sep 2014 08:33:17 +0200 [thread overview]
Message-ID: <542265AD.1000005@canonical.com> (raw)
In-Reply-To: <CAN8cciZHw69AfLJGKB-e7e=PAw7Jqx7bDmAvfVP=NUuw3xwdeQ@mail.gmail.com>
On 2014-09-24 05:31, Raymond Yau wrote:
> >
> > If one input has a boost and another one has not, and they're equal
> > otherwise, it's more likely you want to use the input with the boost
> > as your primary input.
> >
> > See
> hda-emu.git/codecs/canonical/cx20590-lenovo-20b2z00bus-ccert-201305-13496
> > for an example.
>
> Is this a firmware bug since your firmware 1.02 have two internal Mic
> 0x1e and 0x23 but firmware 1.09 only have one internal mic 0x23
>
> http://www.alsa-project.org/db/?f=a265ed3ac422c0ea77b0ada8596338c6421b4de1
>
> Cannot detect the codec with firmware 1.10
>
> http://www.alsa-project.org/db/?f=a60449e5a19b3dbb7a422defd5a9d51f56216693
>
> The proper fix is remove the redundant internal Mic since auto Mic is
> disabled
The E545 has dual-array mics, so probably both pins are actual internal
mics.
It seems reasonable that upgrading the firmware would also resolve this
problem, but either way I believe this is a good patch for potentially
future codecs in the same situation.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2014-09-24 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 8:38 [PATCH 1/2] ALSA: hda - Move the function "check_amp_caps" to hda_codec.c David Henningsson
2014-09-23 8:38 ` [PATCH 2/2] ALSA: hda - Sort input pins depending on amp caps David Henningsson
2014-09-24 3:31 ` Raymond Yau
2014-09-24 6:33 ` David Henningsson [this message]
2014-09-24 8:59 ` Raymond Yau
2014-09-23 13:58 ` [PATCH 1/2] ALSA: hda - Move the function "check_amp_caps" to hda_codec.c Takashi Iwai
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=542265AD.1000005@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=superquad.vortex2@gmail.com \
--cc=tiwai@suse.de \
/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.