linux-kernel - Re: [PATCH] ALSA: usb-audio: Fix control names for Plantronics/Poly Headsets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4717b9c4-8d9f-40d8-903e-68be30ac7d82@cosmicgizmosystems.com>
Date: Thu, 14 Nov 2024 10:44:52 -0800
From: Terry Junge <linuxhid@...micgizmosystems.com>
To: Takashi Iwai <tiwai@...e.de>, Wade Wang <wade.wang@...com>
Cc: perex@...ex.cz, tiwai@...e.com, kl@...wtf, wangdicheng@...inos.cn,
 k.kosik@...look.com, linux-sound@...r.kernel.org,
 linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] ALSA: usb-audio: Fix control names for Plantronics/Poly
 Headsets

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@...micgizmosystems.com>
>> Signed-off-by: Wade Wang <wade.wang@...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.

> 
> Also, are you sure that this can be applied to all devices of
> Plantonics & co?  Including the devices in future.  I thought they had
> so many different models.

Yes, the quirk only modifies the control names that contain certain keywords.
Additional keywords may have to be added to the list in the future.

> 
> Last but not least, __build_feature_ctl() is no right place to add the
> vendor-specific stuff.  There is already a common place in
> mixer_quirks.c, e.g. snd_usb_mixer_fu_apply_quirk().  Please move the
> fix-up to the appropriate place.

I figured as much and I am currently testing with the function updated
and moved to mixer_quirks.c and will be triggered by snd_usb_mixer_fu_apply_quirk().

> 
> 
> thanks,
> 
> Takashi
> 
>> ---
>>  sound/usb/mixer.c | 30 ++++++++++++++++++++++++++++++
>>  1 file changed, 30 insertions(+)
>>
>> diff --git a/sound/usb/mixer.c b/sound/usb/mixer.c
>> index bd67027c7677..110d43ace4d8 100644
>> --- a/sound/usb/mixer.c
>> +++ b/sound/usb/mixer.c
>> @@ -1664,6 +1664,33 @@ static void check_no_speaker_on_headset(struct snd_kcontrol *kctl,
>>  	snd_ctl_rename(card, kctl, "Headphone");
>>  }
>>  
>> +static void fix_plt_control_name(struct snd_kcontrol *kctl)
>> +{
>> +	static const char * const names_to_remove[] = {
>> +		"Earphone",
>> +		"Microphone",
>> +		"Receive",
>> +		"Transmit",
>> +		NULL
>> +	};
>> +	const char * const *n2r;
>> +	char *dst, *src;
>> +	size_t len;
>> +
>> +	for (n2r = names_to_remove; *n2r; ++n2r) {
>> +		dst = strstr(kctl->id.name, *n2r);
>> +		if (dst != NULL) {
>> +			src = dst + strlen(*n2r);
>> +			len = strlen(src) + 1;
>> +			if ((char *)kctl->id.name != dst && *(dst - 1) == ' ')
>> +				--dst;
>> +			memmove(dst, src, len);
>> +		}
>> +	}
>> +	if (kctl->id.name[0] == '\0')
>> +		strscpy(kctl->id.name, "Headset", SNDRV_CTL_ELEM_ID_NAME_MAXLEN);
>> +}
>> +
>>  static const struct usb_feature_control_info *get_feature_control_info(int control)
>>  {
>>  	int i;
>> @@ -1780,6 +1807,9 @@ static void __build_feature_ctl(struct usb_mixer_interface *mixer,
>>  		if (!mapped_name)
>>  			check_no_speaker_on_headset(kctl, mixer->chip->card);
>>  
>> +		if (USB_ID_VENDOR(mixer->chip->usb_id) == 0x047f)
>> +			fix_plt_control_name(kctl);
>> +
>>  		/*
>>  		 * determine the stream direction:
>>  		 * if the connected output is USB stream, then it's likely a
>> -- 
>> 2.43.0
>>