From: Takashi Iwai <tiwai@suse.de>
To: songxiebing <songxiebing@kylinos.cn>
Cc: tiwai@suse.com, perex@perex.cz, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/generic: Use "Input Source" for the capture source selector
Date: Thu, 22 Oct 2026 11:36:31 +0200 [thread overview]
Message-ID: <87pkx2cc0w.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261022092921.2084573-1-songxiebing@kylinos.cn>
On Thu, 22 Oct 2026 11:29:21 +0200,
songxiebing wrote:
>
> >That can work, but I'd rather check further why PA doesn't work with
> >Capture Source. If it's something like an element that doesn't match
> >with the actual input, it's a driver's problem and we may work around
> >it somehow. But before figuring it out, it's not wise to blindly
> >work around something just because it looks as if working.
> >
> >
> >thanks,
> >
> >Takashi
>
> Thanks for reply.
>
> What I found so far on the userspace side:
>
> - alsa-lib's simple-mixer layer special-cases the exact name "Capture
> Source": it does *not* expose an enumerated element with that name, but
> instead creates one exclusive capture switch per enum item, named after
> the item (simple_none.c, simple_event_add()).
> - PulseAudio's ALSA backend resolves its "Capture Source" element strictly
> by name (element_probe() -> snd_mixer_find_selem()), so it never finds
> an element and the mux is never switched. PA also has no handling for
> snd_mixer_selem_has_capture_switch_exclusive(), so it can't consume the
> per-item switches either.
If that's true, PA is broken for all other AC97-based PCI cards?
Let's verify the PA behavior more at first.
Takashi
prev parent reply other threads:[~2026-10-22 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 2:57 songxiebing
2026-10-22 6:13 ` Takashi Iwai
2026-10-22 8:09 ` songxiebing
2026-10-22 8:29 ` Takashi Iwai
2026-10-22 9:29 ` songxiebing
2026-10-22 9:36 ` Takashi Iwai [this message]
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=87pkx2cc0w.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=songxiebing@kylinos.cn \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®