public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: ddstreet@ieee.org
Cc: David Brownell <david-b@pacbell.net>,
	linux-usb-devel@lists.sourceforge.net,
	Alan Stern <stern@rowland.harvard.edu>,
	Bodo Eggert <7eggert@gmx.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] Re: EHCI TT bandwidth (was Re: [PATCH] USB_BANDWIDTH documentation change)
Date: Fri, 30 Dec 2005 14:16:38 -0500	[thread overview]
Message-ID: <1135970198.31111.18.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.51.0512301407200.28360@dylan.root.cx>

On Fri, 2005-12-30 at 14:13 -0500, Dan Streetman wrote:
> On Thu, 29 Dec 2005, Lee Revell wrote:
> 
> >How do I test them?  Should this make USB audio work with
> >CONFIG_USB_BANDWIDTH?
> 
> It won't have any effect on CONFIG_USB_BANDWIDTH, as the EHCI transaction 
> translator scheudling code doesn't care about that config setting.  This 
> also won't have any effect on USB 2.0 devices (e.g. a highspeed Audio 
> device).
> 
> The updates will only help in the situation where there are multiple
> lowpseed or fullspeed devices with periodic endpoints, all connected to
> the same USB 2.0 (highspeed) hub.  In that situation it's possible to
> "fill up" the USB 2.0 hub's transaction translator periodic schedule with
> only a few devices.  The updates allow many more devices to fit in the
> TT's periodic schedule.  The specific number of devices depends on how 
> many periodic endpoints, those endpoint's poll rates, and their max packet 
> sizes.
> 

OK.  For some reason I though that problem was fixed, I guess it was a
different issue.  ALSA users previously reported that a full speed audio
device didn't work at all through a high speed hub at all but that it
was fixed a few months ago.

Lee


  reply	other threads:[~2005-12-30 19:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 10:25 [PATCH] USB_BANDWIDTH documentation change Bodo Eggert
2005-12-26 15:06 ` Lee Revell
2005-12-26 21:49   ` Bodo Eggert
2005-12-26 22:35     ` Alan Stern
2005-12-27  4:17       ` Greg KH
2005-12-27 17:02         ` [linux-usb-devel] " David Brownell
2005-12-27 16:57       ` David Brownell
2005-12-29 19:41         ` EHCI TT bandwidth (was Re: [PATCH] USB_BANDWIDTH documentation change) Dan Streetman
2005-12-29 20:05           ` Lee Revell
2005-12-30 19:13             ` [linux-usb-devel] " Dan Streetman
2005-12-30 19:16               ` Lee Revell [this message]
2005-12-29 20:12           ` David Brownell
2005-12-30  0:56             ` Dan Streetman

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=1135970198.31111.18.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=7eggert@gmx.de \
    --cc=david-b@pacbell.net \
    --cc=ddstreet@ieee.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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