From: David Henningsson <david.henningsson@canonical.com>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: HDA: Fix front mic on Dell Precision M6500
Date: Tue, 24 Aug 2010 08:04:23 +0200 [thread overview]
Message-ID: <4C7360E7.6060300@canonical.com> (raw)
In-Reply-To: <AANLkTin4X_gNKCeuEbFZ87QcUybx+AuGV7HSaXNEZsLT@mail.gmail.com>
2010-08-24 02:57, Raymond Yau skrev:
> 2010/8/24 David Henningsson <david.henningsson@canonical.com>
>
>> I admit that the best thing would be to make the driver support all
>> three mics, but at this point, the alsa driver can only support two, one
>> called "mic" and one called "front mic". I believe the best choice is to
>> select the internal mic as "front mic" and the mic jack on the laptop as
>> "mic", thus leaving the docking station mic jack non-functional.
>>
>> The behavior without this patch is to select the mic jack on the laptop
>> as "mic" and the mic on the docking station as "front mic", thus leaving
>> the internal mic non-functional in all cases, and that regardless of you
>> have a docking station or not.
>>
>> 2010-08-23 21:07, Jerone Young skrev:
>>> For laptops you would want to take preference of the docking jack over
>>> the interal mic if you are in a docking station.
>>>
>>> So if you do plug into a docking station and you have a microphone in
>>> the docking station, a user would want to use that over the internal
>>> microphone. You wouldn't want the laptop internal mic preferred over the
>>> docking station microphone.
>>>
>>> Thanks,
>>> Jerone
>>>
>>> On Mon, 2010-08-23 at 21:03 +0200, David Henningsson wrote:
>>>> The BIOS of Dell Precision M6500 lists both 0x0e and 0x11 as
>>>> front mics, and the driver only supports one front mic. This
>>>> commit adds a quirk for preferring node 0x11 (internal mic) to
>>>> node 0x0e (possibly docking station mic).
>>>>
>>>> Alsa-info reference:
>>>> http://launchpadlibrarian.net/54232083/alsa-info.txt.xyFVpIysHt
>>>>
>>
>
> There are two ADC , this mean that the correct model should provide two
> capture subdevices instead of one
>
> Node 0x15 [Audio Input] wcaps 0x1d0541: Stereo
> Device: name="STAC92xx Analog", type="Audio", device=0
> Converter: stream=1, channel=0
> SDI-Select: 0
> Power: setting=D0, actual=D0
> Delay: 13 samples
> Connection: 1
> 0x17
> Processing caps: benign=0, ncoeff=0
> Node 0x16 [Audio Input] wcaps 0x1d0541: Stereo
> Converter: stream=0, channel=0
> SDI-Select: 0
> Power: setting=D0, actual=D0
> Delay: 13 samples
> Connection: 1
> 0x18
> Processing caps: benign=0, ncoeff=0
I don't disagree. Feel free to write a patch for that, I assume Takashi
will take it if it's written well enough and according to his/Linus's
standards.
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2010-08-24 6:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 19:03 [PATCH] ALSA: HDA: Fix front mic on Dell Precision M6500 David Henningsson
2010-08-23 19:07 ` Jerone Young
2010-08-23 19:25 ` David Henningsson
2010-08-24 0:57 ` Raymond Yau
2010-08-24 6:04 ` David Henningsson [this message]
2010-08-24 13:20 ` Raymond Yau
2010-08-26 10:20 ` Takashi Iwai
2010-08-26 10:22 ` Takashi Iwai
2010-08-30 16:58 ` Takashi Iwai
2010-08-31 9:01 ` David Henningsson
2010-08-31 9:10 ` Takashi Iwai
2010-09-03 3:43 ` David Henningsson
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=4C7360E7.6060300@canonical.com \
--to=david.henningsson@canonical.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).