All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Terry Junge <linuxhid@cosmicgizmosystems.com>
Cc: Takashi Iwai <tiwai@suse.de>, Wade Wang <wade.wang@hp.com>,
	perex@perex.cz, tiwai@suse.com, kl@kl.wtf,
	wangdicheng@kylinos.cn, k.kosik@outlook.com,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: usb-audio: Fix control names for Plantronics/Poly Headsets
Date: Fri, 15 Nov 2024 09:19:57 +0100	[thread overview]
Message-ID: <87jzd4syc2.wl-tiwai@suse.de> (raw)
In-Reply-To: <4717b9c4-8d9f-40d8-903e-68be30ac7d82@cosmicgizmosystems.com>

On Thu, 14 Nov 2024 19:44:52 +0100,
Terry Junge wrote:
> 
> Thanks Takashi,
> 
> On 11/13/24 11:10 PM, Takashi Iwai wrote:
> > On Thu, 14 Nov 2024 07:15:53 +0100,
> > Wade Wang wrote:
> >>
> >> Add a control name fixer for all headsets with VID 0x047F.
> >>
> >> Signed-off-by: Terry Junge <linuxhid@cosmicgizmosystems.com>
> >> Signed-off-by: Wade Wang <wade.wang@hp.com>
> > 
> > Thanks for the patch, but from the description, it's not clear what
> > this patch actually does.  What's the control name fixer and how it
> > behaves?
> 
> It will be better described in the v2 patch.
> 
> It modifies names like
> 
> Headset Earphone Playback Volume
> Headset Microphone Capture Switch
> Receive Playback Volume
> Transmit Capture Switch
> 
> to
> 
> Headset Playback Volume
> Headset Capture Switch
> 
> so user space will bind to the headset's audio controls.

OK, that makes sense.  I suppose that both "Headset Earphone Playback
Volume" and "Receive Playback Volume" don't exist at the same time,
right?


Takashi

  reply	other threads:[~2024-11-15  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14  6:15 [PATCH] ALSA: usb-audio: Fix control names for Plantronics/Poly Headsets Wade Wang
2024-11-14  6:32 ` kernel test robot
2024-11-14  7:10 ` Takashi Iwai
2024-11-14 18:44   ` Terry Junge
2024-11-15  8:19     ` Takashi Iwai [this message]
2024-11-16  2:10       ` Terry Junge

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=87jzd4syc2.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=k.kosik@outlook.com \
    --cc=kl@kl.wtf \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linuxhid@cosmicgizmosystems.com \
    --cc=perex@perex.cz \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=wade.wang@hp.com \
    --cc=wangdicheng@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 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.