From: Mark Brown <broonie@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Takashi Iwai <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.com>
Subject: Re: DAPM PIN switches do not update in alsamixer when changed through UCM profile
Date: Mon, 4 Oct 2021 13:58:06 +0100 [thread overview]
Message-ID: <YVr6Xkm0tm0IghON@sirena.org.uk> (raw)
In-Reply-To: <8e0a6491-bc87-0f9a-099f-3baff1fc0e0d@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On Sun, Oct 03, 2021 at 06:32:13PM +0200, Hans de Goede wrote:
> On 10/3/21 4:46 PM, Takashi Iwai wrote:
> But it does not work for the "Headphone" and "Line Out" switches,
> these are actually hooked up to jack-detect, so I guess that the
> jack-detection is already flipping them and then when the UCM
> profile changes them it is a no-op causing the UCM setting of
> the control to not cause an event because it is not a change.
It's not meaningful or sensible to have a pin switch and jack detection
connected to the same pin, any machine driver doing that is buggy. It's
unclear how the two would be supposed to interact and there's nothing
that makes an effort to keep them in sync. Either jack detection should
be disconnected from DAPM and userspace responsible for managing the
paths via the pin switches or the pin switches should be removed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-10-04 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 13:12 DAPM PIN switches do not update in alsamixer when changed through UCM profile Hans de Goede
2021-10-03 14:46 ` Takashi Iwai
2021-10-03 16:32 ` Hans de Goede
2021-10-04 6:43 ` Takashi Iwai
2021-10-04 12:58 ` Mark Brown [this message]
2021-10-07 10:51 ` Hans de Goede
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=YVr6Xkm0tm0IghON@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=hdegoede@redhat.com \
--cc=tiwai@suse.com \
--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 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.