Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Zhang Heng <zhangheng@kylinos.cn>
Cc: perex@perex.cz, tiwai@suse.com, cryolitia.pukngae@linux.dev,
	kuninori.morimoto.gx@renesas.com, lhi0729@kaist.ac.kr,
	pav@iki.fi, rene@exactco.de, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: usb-audio: Add Line Out to iterm_names
Date: Wed, 31 Dec 2025 16:43:18 +0100	[thread overview]
Message-ID: <87ecoay7vt.wl-tiwai@suse.de> (raw)
In-Reply-To: <20251229093130.3202058-1-zhangheng@kylinos.cn>

On Mon, 29 Dec 2025 10:31:29 +0100,
Zhang Heng wrote:
> 
> There are three jack events for a sound card on a desktop computer,
> namely Speaker, Headphone, and Desktop Speaker. When both audio
> devices are available, users cannot distinguish which audio device
> is being used. Can we consider adding Line Out? similar to the HDA
> sound card. This can change one of them and reduce the complexity
> of the upper layer adaptation of the sound card.
> 
> Signed-off-by: Zhang Heng <zhangheng@kylinos.cn>

Is 0x0308 something properly defined standard?  
If so, we can add the entry, of course.


thanks,

Takashi


> ---
>  sound/usb/mixer.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/sound/usb/mixer.c b/sound/usb/mixer.c
> index 3af71d42b9b9..bdde4261d994 100644
> --- a/sound/usb/mixer.c
> +++ b/sound/usb/mixer.c
> @@ -615,6 +615,7 @@ static struct iterm_name_combo {
>  	{ 0x0305, "Room Speaker" },
>  	{ 0x0306, "Com Speaker" },
>  	{ 0x0307, "LFE" },
> +	{ 0x0308, "Line Out" },
>  	{ 0x0600, "External In" },
>  	{ 0x0601, "Analog In" },
>  	{ 0x0602, "Digital In" },
> -- 
> 2.47.1
> 

  reply	other threads:[~2025-12-31 15:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29  9:31 [PATCH] ALSA: usb-audio: Add Line Out to iterm_names Zhang Heng
2025-12-31 15:43 ` Takashi Iwai [this message]
2026-01-01  1:18   ` zhangheng
2026-01-01 10:03     ` Takashi Iwai
2026-01-01 11:40     ` Jaroslav Kysela
2026-01-04  7:21       ` zhangheng
2026-01-14  8:01       ` zhangheng
2026-01-14  8:11         ` Jaroslav Kysela
2026-01-14  9:22           ` zhangheng

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=87ecoay7vt.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=cryolitia.pukngae@linux.dev \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lhi0729@kaist.ac.kr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=pav@iki.fi \
    --cc=perex@perex.cz \
    --cc=rene@exactco.de \
    --cc=tiwai@suse.com \
    --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