From: Clemens Ladisch <clemens@ladisch.de>
To: Monty Montgomery <xiphmont@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: A problem with USB audio devices and the UHCI scheduler
Date: Wed, 04 Jul 2012 15:43:04 +0200 [thread overview]
Message-ID: <4FF44868.70506@ladisch.de> (raw)
In-Reply-To: <CACrD=+-NB0Lyd=BAAC7D304fUA6xj-OZOao5_9B96C5ffi2osA@mail.gmail.com>
Monty Montgomery wrote:
> The device does use altsets for different sample formats and
> input/output channels, just not altsets for each sample rate (as
> supported/encouraged by the Audio Class...
Supported, but not encouraged:
| A typical use of alternate settings is to provide a way to change
| the bandwidth requirements an active AudioStreaming interface
| imposes on the USB.
> Is it really the case that other Audio Class devices never make use
> of the "multiple sample rates in an altset" feature?
They do, but not when bandwidth matters.
Regards,
Clemens
prev parent reply other threads:[~2012-07-04 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 1:05 A problem with USB audio devices and the UHCI scheduler Monty Montgomery
2012-07-03 17:47 ` Clemens Ladisch
2012-07-03 18:13 ` Monty Montgomery
2012-07-04 13:43 ` Clemens Ladisch [this message]
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=4FF44868.70506@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=xiphmont@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox