All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: HDA intel, wired headset w/mic, jack mic detect
Date: Thu, 15 Mar 2012 11:03:03 -0700	[thread overview]
Message-ID: <87bonxbv3c.fsf@ti.com> (raw)
In-Reply-To: <CAN8cciZqB3oVVGMS4=RBSGZH+nSJAZoUT_a8hFu=pBnNJ3gwfw@mail.gmail.com> (Raymond Yau's message of "Wed, 14 Mar 2012 08:50:53 +0800")

Raymond Yau <superquad.vortex2@gmail.com> writes:

> 2012/3/10, Kevin Hilman <khilman@ti.com>:
>>
>> Ah, that's a little easier to tinker with for the uninformed like me. :)
>>
>> Using that, it seems that the above registers work on my coded (cs4206)
>> too.  I was able to determine that the built-in mic is ADC2 right
>> channel, and can at least make the built-in mic switch from the right to
>> left (swap channel mode)
>>
>>     sudo hda-verb /dev/snd/hwC0D0 0x11 SET_COEF_INDEX 2
>>     sudo hda-verb /dev/snd/hwC0D0 0x11 SET_PROC_COEF 0x180a
>>
>> or make the right channel go to both HDA channels (mono mode):
>>
>>     sudo hda-verb /dev/snd/hwC0D0 0x11 SET_COEF_INDEX 2
>>     sudo hda-verb /dev/snd/hwC0D0 0x11 SET_PROC_COEF 0x100a
>>
>> However, I still can't figure out where the headset mic is and how to
>> enable it.
>>
>> Here's what I think I know (c.f. alsa-info.sh  output below)
>>
>
> do you mean that you cannot record mono using sysdefault  which use a
> route to copy left channel channel to both if the internal mic is at
> the right channel?
>
> arecord --vumeter=mono -c 1 -f S16_LE -r 48000 -Dsysdefault /dev/null

Not sure exactly what you mean by sysdefault, but trying that fails:

$ arecord --vumeter=mono -c 1 -f S16_LE -r 48000 -Dsysdefault /dev/null
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM sysdefault
arecord: main:660: audio open error: No such file or directory

Kevin

  reply	other threads:[~2012-03-15 18:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 19:09 HDA intel, wired headset w/mic, jack mic detect Kevin Hilman
2012-02-24  6:25 ` David Henningsson
2012-02-28 17:55   ` Hilman, Kevin
2012-02-28 18:00     ` Mark Brown
2012-02-29 15:05     ` Raymond Yau
2012-02-29 15:26       ` Mark Brown
2012-02-29 19:08       ` Kevin Hilman
2012-02-29 23:43         ` Raymond Yau
2012-03-01  1:34           ` Kevin Hilman
2012-03-01  5:56             ` Raymond Yau
2012-03-01 18:22               ` Kevin Hilman
2012-03-02  1:22                 ` Raymond Yau
2012-03-02 19:32                   ` Kevin Hilman
2012-03-05  1:10                     ` Raymond Yau
2012-03-05 17:36                       ` Kevin Hilman
2012-03-06  1:28                         ` Raymond Yau
2012-03-06  6:44                           ` Takashi Iwai
2012-03-06 20:25                             ` Kevin Hilman
2012-03-06 20:32                               ` Takashi Iwai
2012-03-09 17:16                                 ` Kevin Hilman
2012-03-14  0:50                                   ` Raymond Yau
2012-03-15 18:03                                     ` Kevin Hilman [this message]
2012-03-15 23:57                                       ` Raymond Yau
2012-03-20 18:14                                     ` Kevin Hilman
2012-03-01 17:25         ` Mark Brown
2012-03-01 17:46           ` Kevin Hilman

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=87bonxbv3c.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=superquad.vortex2@gmail.com \
    /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.