From: Zipdox <zipdox@zipdox.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-sound@vger.kernel.org, perex@perex.cz,
linux-kernel@vger.kernel.org, tiwai@suse.com
Subject: Re: [PATCH] USB Audio Class 2 Mixer unit support for GET_CUR, SET_CUR and RANGE
Date: Wed, 16 Sep 2026 09:43:14 +0200 [thread overview]
Message-ID: <da56664f-901e-497b-a74c-ae41cbc5cac4@zipdox.net> (raw)
In-Reply-To: <8733vamwaz.wl-tiwai@suse.de>
On 9/15/26 4:19 PM, Takashi Iwai wrote:
> But your code also blindly assumes the MU_MIXER_CONTROL that doesn't
> fit with other units like feature unit? I guess we have to set the
> proper Control Selector value depending on the unit type.
>
> After all, this is about the correct setup of wValue. Let's try to be
> minimalistic at first -- just tweak wValue in get_ctl_value_v2() and
> snd_usb_mixer_set_ctl_value() at first. If this becomes too ugly, we
> can think of redesigning.
I assumed that mixer.c was just for the mixer unit, and I seem to have
completely overlooked the fact that that it also controls feature units.
I'm not sure how to proceed from here. Do you have any suggestions for
how we can store the control selector in the usb_mixer_elem_info struct?
The control field is presently used as the input channel number, so
maybe we should add a separate field for the input channel? I think
maybe it's better that someone else fixes this, I'm kind of out of my
element here.
next prev parent reply other threads:[~2026-09-16 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 8:54 Zipdox
2026-09-15 11:08 ` Takashi Iwai
2026-09-15 12:54 ` Zipdox
2026-09-15 14:19 ` Takashi Iwai
2026-09-16 7:43 ` Zipdox [this message]
2026-09-16 15:40 ` Takashi Iwai
2026-09-16 16:58 ` Takashi Iwai
2026-09-16 18:22 ` Takashi Iwai
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=da56664f-901e-497b-a74c-ae41cbc5cac4@zipdox.net \
--to=zipdox@zipdox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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®