The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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 10:29:18 +0200	[thread overview]
Message-ID: <87y0bqcf4x.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261022080904.1740256-1-songxiebing@kylinos.cn>

On Thu, 22 Oct 2026 10:09:04 +0200,
songxiebing wrote:
> 
> >It must be rather a problem of PulseAudio, and it should be able to
> >handle Capture Source, as it's been used for most of old AC97-based
> >cards.
> >
> >Reverting this old behavior change (since 14 years ago!) is just
> >no-go.
> >
> >
> >thanks,
> >
> >Takashi
> 
> Thank you for reply.  You are right -- changing the name
> unconditionally was not well thought out, and I agree that reverting the
> long-standing behavior is not acceptable.
> 
> Would it be acceptable if I add a flag to hda_gen_spec (e.g.
> use_input_source) that decides whether to use "Input Source" for the
> capture source selector?  A codec driver could set it when needed, while
> the default behavior stays unchanged.

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

  reply	other threads:[~2026-10-22  8:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22  2:57 [PATCH] ALSA: hda/generic: Use "Input Source" for the capture source selector songxiebing
2026-10-22  6:13 ` Takashi Iwai
2026-10-22  8:09 ` songxiebing
2026-10-22  8:29   ` Takashi Iwai [this message]
2026-10-22  9:29 ` songxiebing
2026-10-22  9:36   ` Takashi Iwai
2026-10-27  2:22 ` songxiebing
2026-10-27  8:38 ` songxiebing

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=87y0bqcf4x.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