Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: Jan Baumgart <raga.raga@gmx.de>, alsa-devel@alsa-project.org
Subject: Re: MiniDSP USBStreamer / UAC2 / Alsamixer bogus
Date: Fri, 23 May 2014 19:18:05 +0200	[thread overview]
Message-ID: <537F82CD.6010907@zonque.org> (raw)
In-Reply-To: <trinity-69d5b18f-8b7a-4d6a-97e4-025a61f952fe-1400780207708@3capp-gmx-bs24>

Hi,

On 05/22/2014 07:36 PM, Jan Baumgart wrote:
>          AudioControl Interface Descriptor:
>            bLength                16
>            bDescriptorType        36
>            bDescriptorSubtype      9 (EXTENSION_UNIT)
>          Warning: Descriptor too short

Hmm, lsusb is right here - bLength should be 16+p ...

>            bUnitID                51
>            wExtensionCode          0
>            bNrPins                 1

... where p is this value: 1.

>            baSourceID( 0)          2
>            bNrChannels             8
>            wChannelConfig          0
>            iChannelNames           3
>            bmControls        0x00
>            iExtension             42

Hence, the iExtension value is wrong, ...

>          AudioControl Interface Descriptor:
>            bLength                42

because it actually is bLength of the next descriptor. So there's
definitely a problem in the USB descriptors, I'm just not sure how we
should deal with that.

I'm also not entirely sure if that explains your control name trouble.
If you're interested in debugging this, have a look at the function
sound/usb/mixer.c, function build_audio_procunit(), especially the lower
half where we try to determine a nice name for the new control. You
could start dumping the variable 'nameid' and see what it contains.

Also, this device reports strings to describe the channel names
(iChannelNames), which the driver currently doesn't care about. It might
be worth fetching them and see what they contain. On the other hand,
ALSA doesn't allow us to provide names for individual sub-controls (for
each of the 8 mixer values inside one control).

Are you up for a little trial and error? I doubt that this will fix your
clock selector trouble though, but for that, the usbmon traces should
give a hint.


Best regards,
Daniel

  parent reply	other threads:[~2014-05-23 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 17:36 MiniDSP USBStreamer / UAC2 / Alsamixer bogus Jan Baumgart
2014-05-23 10:10 ` Daniel Mack
2014-05-23 17:18 ` Daniel Mack [this message]
2014-05-24 10:22   ` Jan Baumgart

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=537F82CD.6010907@zonque.org \
    --to=daniel@zonque.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=raga.raga@gmx.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