Skip to contentSkip to conversation

ALSA: usb-audio: Add quirk flag for Creative Stage SE

PATCH In review Yejung Kim 2 participants 3 messages Oct 2 – Oct 3 Sound

lore
Share & tools
lore

Yejung Kim

author
#0 lore raw

PATCH 1/1 ALSA: usb-audio: Add quirk flag for Creative Stage SE

The UAC mixer on Creative Stage SE (041e:3289) returns invalid/constant GET_CUR volume values, causing ALSA to treat it as a sticky mixer and to disable it.

Add a quirk table entry applying QUIRK_FLAG_MIXER_GET_CUR_BROKEN to allow volume controls to function correctly.

---
 sound/usb/quirks.c | 2 ++
 1 file changed, 2 insertions(+)
sound/usb/quirks.c +2 -0
index c5870901a8d4..961038f08890 100644
@@ -2242,6 +2242,8 @@ static const struct usb_audio_quirk_flags_table quirk_flags_table[] = {
 		   QUIRK_FLAG_IGNORE_CTL_ERROR),
 	DEVICE_FLG(0x041e, 0x324d, /* Creative Sound Blaster Play! 3 */
 		   QUIRK_FLAG_MIXER_PLAYBACK_MIN_MUTE),
+	DEVICE_FLG(0x041e, 0x3289, /* Creative Stage SE */
+		   QUIRK_FLAG_MIXER_GET_CUR_BROKEN),
 	DEVICE_FLG(0x041e, 0x4080, /* Creative Live Cam VF0610 */
 		   QUIRK_FLAG_GET_SAMPLE_RATE),
 	DEVICE_FLG(0x045e, 0x083c, /* MS USB Link headset */
Signature · 1 line
2.56.0
#1 lore raw
Quoted 9 lines · Yejung Kim

The UAC mixer on Creative Stage SE (041e:3289) returns invalid/constant GET_CUR volume values, causing ALSA to treat it as a sticky mixer and to disable it.

Add a quirk table entry applying QUIRK_FLAG_MIXER_GET_CUR_BROKEN to allow volume controls to function correctly.

Applied now. Thanks.

Takashi

#2 lore raw
Quoted 8 lines · Takashi Iwai
Quoted 5 lines · Yejung Kim

The UAC mixer on Creative Stage SE (041e:3289) returns invalid/constant GET_CUR volume values, causing ALSA to treat it as a sticky mixer and to disable it.

Quoted 6 lines
Quoted 4 lines

Add a quirk table entry applying QUIRK_FLAG_MIXER_GET_CUR_BROKEN to allow volume controls to function correctly.

Applied now. Thanks.

... rather not, I dropped again.

This flag is no longer needed with the latest 7.3-rc, and the quirk has been dropped / renamed.

Please retest with the latest 7.3-rc. Or it'll be fixed in the upcoming 7.2.x update, I suppose.

thanks,

Takashi