mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Takashi Iwai <tiwai@suse.de>, Zhang Heng <zhangheng@kylinos.cn>
Cc: tiwai@suse.com, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Fwd: [PATCH] ALSA: hda/generic: Add mic autoswitch support for dyn_adc_switch mode
Date: Fri, 15 May 2026 13:19:57 +0200	[thread overview]
Message-ID: <7698e8ba-974b-4bdd-a2ce-21a32e50c1de@perex.cz> (raw)
In-Reply-To: <87ecjdt487.wl-tiwai@suse.de>

On 5/15/26 11:24, Takashi Iwai wrote:
> On Fri, 08 May 2026 04:50:22 +0200,
> Zhang Heng wrote:
>>
>> I tested this change:
>>
>> In create_capture_mixers in generic.c:
>>
>> - name = nums > 1 ? "Input Source" : "Capture Source";
>> + name = "Input Source";
>>
>> And it also works normally. It seems that user-space does not handle
>> "Capture Source" very well. So should we just remove "Capture Source"?
> 
> If this really works, it is rather a question to user-space behavior,
> specifically alsa-lib's interpretation.

It's more likely the app interpretation (PA/PW) rather than alsa-lib. The 
"Input Source" means that there are more capture PCM devices and those 
controls distinguish the input sources for them.

It would be nice to see the 'amixer controls' output to see more details what 
the driver exposes to the user space.

					Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

  reply	other threads:[~2026-05-15 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5b215802-4c94-4f94-9cee-f8e497b31337@kylinos.cn>
2026-05-06  7:03 ` Zhang Heng
2026-05-07 15:05   ` Takashi Iwai
2026-05-08  2:21     ` Zhang Heng
2026-05-08  2:50       ` Zhang Heng
2026-05-15  9:24         ` Takashi Iwai
2026-05-15 11:19           ` Jaroslav Kysela [this message]
2026-05-15 11:29             ` Takashi Iwai
2026-05-18  7:03             ` Zhang Heng
2026-05-18  7:07             ` Zhang Heng

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=7698e8ba-974b-4bdd-a2ce-21a32e50c1de@perex.cz \
    --to=perex@perex.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    --cc=zhangheng@kylinos.cn \
    /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®