From: Daniel Mack <daniel@caiaq.de>
To: Matti Picus <matti.picus@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: S51 usb support
Date: Wed, 6 Oct 2010 00:04:46 +0200 [thread overview]
Message-ID: <20101005220446.GR7159@buzzloop.caiaq.de> (raw)
In-Reply-To: <4CAB787E.1050409@gmail.com>
On Tue, Oct 05, 2010 at 09:11:58PM +0200, Matti Picus wrote:
> On 10/05/2010 09:38 AM, Daniel Mack wrote:
> >
> >Normally, the volume would be controlled by a feature unit. Just post
> >the whole output of 'lsusb -v' to some pastebin website and post the
> >link.
> >
> http://pastebin.com/e8ZcX9TN
Hmm, there is no feature unit in this dump, so the volume is most
probably set with an vendor-specific USB request. Unless the Windows
driver does something similar than PulseAudio and handles the volume
level control in software (iow, modify each sample before sending it to
the hardware) rather than setting any actual hardware volume level.
> >>Any guidance you can give toward getting the volume controls
> >>recognized would be greatly appreciate.
> >The best way is to sniff the USB communication when Windows sets the
> >volume
> Is there an example in the alsa source tree of some of this?
Of a sniff dump you mean? I doubt so, but once you manage to get one
with any of the software tools around or with a hardware analyzer, the
dump itself shouldn't be hard to understand. You just need to understand
the packet layout and where they store the actual volume information.
Once you got this information, feel free to share it, so we can figure
out a nice way of generating the same kind of messages from inside the
kernel driver.
Daniel
next prev parent reply other threads:[~2010-10-05 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 21:22 S51 usb support Matti Picus
2010-10-04 4:41 ` Daniel Mack
2010-10-04 20:08 ` Matti Picus
2010-10-05 7:38 ` Daniel Mack
2010-10-05 19:11 ` Matti Picus
2010-10-05 22:04 ` Daniel Mack [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-20 20:30 Mandar Joshi
2010-10-22 5:14 ` Mandar Joshi
2010-10-23 15:37 ` Mandar Joshi
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=20101005220446.GR7159@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=alsa-devel@alsa-project.org \
--cc=matti.picus@gmail.com \
/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.