From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Broken microphone switch on mtk-rt5650
Date: Thu, 20 Jul 2023 05:54:09 +0200 (CEST) [thread overview]
Message-ID: <20230720035409.DD113F8047D@alsa1.perex.cz> (raw)
In-Reply-To: <1689825246457431078-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #336 was edited from jenneron:
The problem is that both headphones and mic use `JackControl "Headset Jack"` When there are headphones without mic connected it switches to external mic which is not present.
In kernel there appears to be only one switch https://github.com/torvalds/linux/blob/3c8b5861850c734add65233e538d4a8c2dff95d9/sound/soc/mediatek/mt8173/mt8173-rt5650.c#L130-L135 responsible for handling both headphone and microphone. So, how is userspace supposed to distinguish connection of headset and headphones?
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/336
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2023-07-20 3:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1689825246457431078-webhooks-bot@alsa-project.org>
2023-07-20 3:54 ` GitHub issues - edited [this message]
[not found] <1689825115049217224-webhooks-bot@alsa-project.org>
2023-07-20 3:52 ` Broken microphone switch on mtk-rt5650 GitHub issues - opened
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=20230720035409.DD113F8047D@alsa1.perex.cz \
--to=github@alsa-project.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