Re: 2.6.11, USB: High latency?

From: David Brownell (david-b_at_pacbell.net)
Date: 03/31/05

  • Next message: Lee Revell: "Re: 2.6.11, USB: High latency?" 
    To: Lee Revell <rlrevell@joe-job.com>
Date:	Wed, 30 Mar 2005 17:28:09 -0800

    On Wednesday 30 March 2005 4:51 pm, Lee Revell wrote:
    > [cc list restored]

    Thanks, I never had one to start with ... :)

    > On Wed, 2005-03-30 at 14:57 -0800, David Brownell wrote:
    > > Quoth rlevell@joe-job.com:
    > > > I think this is connected to a problem people have been reporting on the
    > > > Linux audio lists. With some USB chipsets, USB audio interfaces just
    > > > don't work. There are dropouts even at very high latencies.
    > >
    > > Well, I'd not yet expect USB audio to work over EHCI quite yet,
    > > though one of the patches Greg just posted should help some of
    > > the issues with full speed iso through USB 2.0 hubs. (At least
    > > for OUT transfers as to speakers.)
    > >
    >
    > This is the exact configuration of one of the users who reported the
    > problem on LAU. Got a pointer to the patch? And what's the issue with
    > IN transfers?

    This is what Greg just posted (and Linus merged into BK, so it'll be
    in BK snapshots starting tomorrow):

      http://marc.theaimsgroup.com/?l=linux-usb-devel&m=111221966815043&w=2

    The issue with IN transfers is that microframe scheduling is ... tricky.
    One must track all kinds of stuff (which TTs are involved, which microframes
    are busy, how busy they are, how much non-TT bandwidth is available). And
    the relevant EHCI data structures are almost as irregular as the USB trees
    one must cope with.

    Plus one must have the time to spend debugging and fixing the problems, stress
    testing the fixes, and devices that will trigger the problems. I've had none
    of those, for quite some time now. (My particular USB speakers have pretty much
    always worked on Linux, even through a USB 2.0 hub.)

    Karsten has some not-ready-for-prime-time patches which he's posted
    recently. They basically hardwire some of the scheduling outputs well
    enough to get some of his IN transfers to work. Maybe he'll be nice
    enough to repost them against current BK (they include the patch above).

    I'd like to see all that split ISO stuff working with EHCI, but someone
    else is going to have to do most of the work. Once it's working we can
    take the CONFIG_EXPERIMENTAL off, which will remove another source of
    errors. :)

    - Dave

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Lee Revell: "Re: 2.6.11, USB: High latency?"

    Relevant Pages

    • Re: 2.6.11, USB: High latency?
      ... > The issue with IN transfers is that microframe scheduling is ... ... > the relevant EHCI data structures are almost as irregular as the USB trees ... > enough to repost them against current BK (they include the patch above). ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: External USB2 HDD affects speed hda
      ... > find whether there are some transfers from host to your USB ... You just need better memory bandwidth so all ... Or maybe EHCI driver ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Extremely poor umass transfer rates
      ... Something is definetly going on with either vfat or the USB drivers... ... To put it plainly, it transfers ... my CF cards do the same thing.. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Very slow umass in 6.2-RC2
      ... Has anyone ever managed to get some USB 2.0 - like speeds out of ehci anyway? ... da2: 40.000MB/s transfers ...
      (freebsd-stable)
    • Still no USB 2.0 with 2.6.14 (on AMD64+nForce4)
      ... Well, the topic says it all: regardless of whichever USB device I plug in, ... it never shows up as a high-speed one using EHCI even if it damn well ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)