All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Nico Schottelius <nico.schottelius@ungleich.ch>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Internal microphone does not work with 5.12 (Tiger Lake, X1 Nano)
Date: Thu, 27 May 2021 09:35:47 -0500	[thread overview]
Message-ID: <a9f03425-cdd7-1a14-fcbe-abdce5e1a21f@linux.intel.com> (raw)
In-Reply-To: <87h7io8e97.fsf@ungleich.ch>




>> arecord -fdat -vv -Dplugw:0,6 -c4 /dev/null
> 
> That does not work:
> 
> [15:55] nb3:~% arecord -fdat -vv -Dplugw:0,6 -c4 /dev/null
> ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM plugw:0,6
> arecord: main:830: audio open error: No such file or directory

typo: you need to use plughw:0,6 or just hw:0,6

> 
> However, recording with audacity produces to results:
> 
> - no sound recorded by default
> - sound recorded when I plugin an external headset
> 
> And using arecord -fdat -vv -c4 /dev/null (without -Dplugw) I get
> output, but the level is always 00% without the headset, ranges 02 ~ 90%
> with the headset plugged in.
> 
> I was wondering if there's a hardware switch "broken"
> for the detection of the headset and that's why the mic is muted
> internally?

No, the DMIC has nothing to do with the headset, it's an independent 
interface.

  reply	other threads:[~2021-05-27 14:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27  9:50 Internal microphone does not work with 5.12 (Tiger Lake, X1 Nano) Nico Schottelius
2021-05-27  9:57 ` Jaroslav Kysela
2021-05-27 10:39   ` Nico Schottelius
2021-05-27 10:56     ` Kai Vehmanen
2021-05-27 12:02       ` Nico Schottelius
2021-05-27 13:43         ` Kai Vehmanen
2021-05-27 14:04           ` Nico Schottelius
2021-05-27 14:35             ` Pierre-Louis Bossart [this message]
2021-05-27 13:55         ` Nico Schottelius

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=a9f03425-cdd7-1a14-fcbe-abdce5e1a21f@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=nico.schottelius@ungleich.ch \
    /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.