Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
	Eliot Blennerhassett <eliot@blennerhassett.gen.nz>
Subject: Re: [RFC PATCH] Inverted internal mic
Date: Thu, 21 Jun 2012 03:15:27 +0200	[thread overview]
Message-ID: <4FE275AF.4080004@canonical.com> (raw)
In-Reply-To: <s5htxy6f6tt.wl%tiwai@suse.de>

On 06/20/2012 03:31 PM, Takashi Iwai wrote:
> At Tue, 19 Jun 2012 09:43:07 +0200,
> David Henningsson wrote:
>>
>> On 06/19/2012 05:07 AM, Eliot Blennerhassett wrote:
>>> David Henningsson<david.henningsson<at>   canonical.com>   writes:
>>>> On 02/28/2012 02:22 PM, Takashi Iwai wrote:
>>>>> At Tue, 28 Feb 2012 14:07:59 +0100,
>>>>> David Henningsson wrote:
>>>>> Is there a way we can
>>>>>> know the corresponding processing coefficients to set for ALC268 and
>>>>>> ALC272X as well?
>>>>>
>>>>> AFAIK, no, it was specific to the codec model.
>>>>
>>>> Ok, then we can only hope for Kailang to supply this information if
>>>> possible. And if not possible we could attempt the workaround (when/if
>>>> we agree on it...) for these devices as well?
>>>
>>> Greetings,
>>>
>>> Any chance that there has been any progress on this?
>>> I have a machine with dmic and ALC272X (details below) that exhibits this
>>> problem, and can test any proposed patch.
>>
>> We have a patch in for the Thinkpad U300s, but that one had a Conexant
>> codec.
>> I haven't had time to start working on kernel patches for the Realtek
>> ones yet, but meanwhile, I'm tracking known machines here:
>>
>> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978
>
> Looking at the codec, it's not so trivial to port the inverted switch
> to Realtek.  In the input path of Realtek codecs, there is no
> individual capture volume/switch but only a central ADC volume and a
> MUX (or a mixer).

Yeah, that's part of why I haven't done it myself yet ;-)

 > I can think of a new boolean switch or an enum to choose whether to
 > shut off the right channel of the input-mux and the loopback volume.
 > But it's feasible only if it make sense to PA.

It seems possible that for ALC269 [1], you could switch path entirely 
(including ADC). I e, the internal mic would go 0x12 -> 0x23 -> 0x08 and 
the external mic would go 0x18 -> 0x24 -> 0x07. That way you could then 
label the volume control on 0x08 "Internal Mic Capture Volume" and 
"Inverted Internal Mic Capture Volume".

Do you think this is a good strategy, or would it lead to other problems 
(i e, what happens when you plug your mic in while actively recording)?

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

[1] Example alsa info: 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/946232/+attachment/3156604/+files/Acer-Aspire-1810TZ__alsa-info.txt

  reply	other threads:[~2012-06-20 23:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28  8:57 [RFC PATCH] Inverted internal mic David Henningsson
2012-02-28  9:24 ` Takashi Iwai
2012-02-28  9:54   ` David Henningsson
2012-02-28 10:38     ` Takashi Iwai
2012-02-28 13:07       ` David Henningsson
2012-02-28 13:22         ` Takashi Iwai
2012-02-28 14:19           ` David Henningsson
2012-02-28 15:20             ` Takashi Iwai
2012-02-28 18:11               ` David Henningsson
2012-02-28 19:42                 ` Takashi Iwai
2012-02-29  9:21                   ` David Henningsson
2012-02-29  9:56                     ` Takashi Iwai
2012-02-29 10:45                       ` David Henningsson
2012-02-29 16:36                         ` Takashi Iwai
2012-06-19  3:07             ` Eliot Blennerhassett
2012-06-19  7:43               ` David Henningsson
2012-06-20 13:31                 ` Takashi Iwai
2012-06-21  1:15                   ` David Henningsson [this message]
2012-06-21 12:52                     ` Takashi Iwai
2012-06-21 13:04                       ` David Henningsson
2012-06-21 13:19                         ` Takashi Iwai
2012-06-21 14:23                           ` David Henningsson
2012-06-22  9:33                             ` Takashi Iwai
2012-06-22 10:46                               ` David Henningsson
2012-06-22 11:00                                 ` Takashi Iwai
2012-06-22 12:46                                   ` Takashi Iwai
2012-06-22 15:27                                     ` David Henningsson
2012-06-22 15:37                                       ` Takashi Iwai
2012-06-22 17:33                                         ` David Henningsson
2012-06-23  2:58                                           ` Eliot Blennerhassett
2012-06-23  8:40                                             ` Takashi Iwai
2012-06-23  8:39                                           ` Takashi Iwai
2012-06-25  8:04                                             ` David Henningsson
2012-06-25  8:18                                               ` Takashi Iwai
2012-06-20  8:02               ` Takashi Iwai
2012-06-20 10:54                 ` Eliot Blennerhassett
2012-02-29 11:02 ` Raymond Yau
2012-06-20 21:53 ` James Courtier-Dutton
2012-06-21  5:56   ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2014-10-20 13:52 rodney byne

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=4FE275AF.4080004@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=eliot@blennerhassett.gen.nz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox