alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Ujjwal Sharma <ryzokuken@disroot.org>
To: alsa-devel@alsa-project.org
Subject: Headset microphone not detected
Date: Fri, 17 Jul 2020 00:01:27 +0530	[thread overview]
Message-ID: <a118fbc5-e9b3-54cc-32f9-217e4077b4b2@disroot.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

Hi everyone!

I am unable to get my headset microphone to work, and that's really
puzzling to me since the headphone speakers show up as plugged and work
perfectly (pulseaudio shows the headset microphone as unplugged).

I reported this issue to the SOF issue tracker on GitHub and they
pointed out that it's an ALSA issue. Here's the mentioned thread:
https://github.com/thesofproject/sof/issues/3164.

My alsa_info.sh: https://pastebin.com/raw/K99520LA

Some snippets from there that might be interesting:

[ 7612.883978] snd_hda_codec_realtek ehdaudio0D0: didn't find PCM for
DAI Digital Codec DAI
[ 7612.883986] snd_hda_codec_realtek ehdaudio0D0: ASoC: can't open DAI
Digital Codec DAI: -22
[ 7612.883992] snd_hda_codec_realtek ehdaudio0D0: didn't find PCM for
DAI Digital Codec DAI
[ 7612.883998]  Digital Playback and Capture: ASoC: BE open failed -22
[ 7612.884002]  HDA Digital: ASoC: failed to start some BEs -22

state.sofhdadsp {
....
		name 'Headset Jack'
		value false
...
		name 'Mic Jack'
		value false

I cannot possibly understand what's wrong. Is it a bug in the codecs?

Thanks,
Ujjwal


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2020-07-16 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 18:31 Ujjwal Sharma [this message]
2020-07-30  6:16 ` Headset microphone not detected Ujjwal Sharma

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=a118fbc5-e9b3-54cc-32f9-217e4077b4b2@disroot.org \
    --to=ryzokuken@disroot.org \
    --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).