Hi Dave, Here is the contend of /sys/class/usb_host/usb1/periodic while play with buzz.
size = 1024 31: qh32-0601/ce4bc300 (f6 ep3in [8/15] q1 p4) 63: qh32-0601/ce4bc300 95: qh32-0601/ce4bc300 127: qh32-0601/ce4bc300 159: qh32-0601/ce4bc300 191: qh32-0601/ce4bc300 223: qh32-0601/ce4bc300 255: qh256-0001/ce4bc100 (h3 ep1in [7/0] q1 p1) qh256-0001/ce4bc200 (h5 ep1in [7/0] q1 p1) qh32-0601/ce4bc300 287: qh32-0601/ce4bc300 319: qh32-0601/ce4bc300 351: qh32-0601/ce4bc300 383: qh32-0601/ce4bc300 415: qh32-0601/ce4bc300 447: qh32-0601/ce4bc300 479: qh32-0601/ce4bc300 496: sitd1-0018/c2a3e120 497: sitd1-0018/c2a3e0c0 498: sitd1-0018/c2a3e060 499: sitd1-0018/c2a3e000 500: sitd1-0018/c2a3e2a0 501: sitd1-0018/c2a3e240 502: sitd1-0018/c2a3e1e0 503: sitd1-0018/c2a3e180 504: sitd1-0018/c2a3e360 505: sitd1-0018/c2a3e300 506: sitd1-0018/c2a3e4e0 507: sitd1-0018/c2a3e480 508: sitd1-0018/c2a3e420 509: sitd1-0018/c2a3e3c0 510: sitd1-0018/c2a3e660 511: sitd1-0018/c2a3e600 qh256-0001/ce4bc100 512: sitd1-0018/c2a3e5a0 513: sitd1-0018/c2a3e540 514: sitd1-0018/c2a3e720 515: sitd1-0018/c2a3e6c0 543: qh32-0601/ce4bc300 575: qh32-0601/ce4bc300 607: qh32-0601/ce4bc300 639: qh32-0601/ce4bc300 671: qh32-0601/ce4bc300 703: qh32-0601/ce4bc300 735: qh32-0601/ce4bc300 767: qh256-0001/ce4bc100 799: qh32-0601/ce4bc300 831: qh32-0601/ce4bc300 863: qh32-0601/ce4bc300 895: qh32-0601/ce4bc300 927: qh32-0601/ce4bc300 959: qh32-0601/ce4bc300 991: qh32-0601/ce4bc300 1023: qh256-0001/ce4bc100 Shiju On Thu, 10 Mar 2005 18:58:16 -0800, David Brownell <[EMAIL PROTECTED]> wrote: > On Thursday 10 March 2005 5:45 pm, Shiju Mathew wrote: > > Hi Dave, > > Here are the details. But I could find that the content of > > /sys/class/usb_host/usb1/periodic remained the same before and after > > playing the audio with buzz. > > Before and after it _should_ be the same unless you've plugged > or unplugged something, or are otherwise changing the set of > active I/O requests. This basically shows a tree of interrupt > transfers; I'd guess a couple high speed hubs and some kind of > full speed HID device, maybe a volume control. > > What I'd need to see is _during_ the play-with-buzz, when there > will be "sitd" entries not just "qh" ones. > > - Dave > > > > [EMAIL PROTECTED] ~]# cat /sys/class/usb_host/usb1/periodic > > size = 1024 > > 31: qh32-0601/ce4b5300 (f6 ep3in [8/15] q1 p4) > > 63: qh32-0601/ce4b5300 > > 95: qh32-0601/ce4b5300 > > 127: qh32-0601/ce4b5300 > > 159: qh32-0601/ce4b5300 > > 191: qh32-0601/ce4b5300 > > 223: qh32-0601/ce4b5300 > > 255: qh256-0001/ce4b5100 (h3 ep1in [7/0] q1 p1) qh256-0001/ce4b5200 > > (h5 ep1in [7/0] q1 p1) qh32-0601/ce4b5300 > > 287: qh32-0601/ce4b5300 > > 319: qh32-0601/ce4b5300 > > 351: qh32-0601/ce4b5300 > > 383: qh32-0601/ce4b5300 > > 415: qh32-0601/ce4b5300 > > 447: qh32-0601/ce4b5300 > > 479: qh32-0601/ce4b5300 > > 511: qh256-0001/ce4b5100 > > 543: qh32-0601/ce4b5300 > > 575: qh32-0601/ce4b5300 > > 607: qh32-0601/ce4b5300 > > 639: qh32-0601/ce4b5300 > > 671: qh32-0601/ce4b5300 > > 703: qh32-0601/ce4b5300 > > 735: qh32-0601/ce4b5300 > > 767: qh256-0001/ce4b5100 > > 799: qh32-0601/ce4b5300 > > 831: qh32-0601/ce4b5300 > > 863: qh32-0601/ce4b5300 > > 895: qh32-0601/ce4b5300 > > 927: qh32-0601/ce4b5300 > > 959: qh32-0601/ce4b5300 > > 991: qh32-0601/ce4b5300 > > 1023: qh256-0001/ce4b5100 > > [EMAIL PROTECTED] ~]# cat > > /sys/class/usb_host/usb1/driver/0000\:00\:1d.7/usb1/version > > 2.00 > > > > Shiju > > > > > > > > > > On Wed, 9 Mar 2005 21:33:06 -0800, David Brownell <[EMAIL PROTECTED]> wrote: > > > On Wednesday 09 March 2005 4:02 pm, Shiju Mathew wrote: > > > > Hi, > > > > I have tried the two patches singly and together . But it did not > > > > resolve the usb audio problem. > > > > > > Well that's annoying. Thanks for trying those; I can't really do > > > much to track this down, since I can't reproduce this. Can you do me a > > > favor and show me the contents of /sys/class/usb_host/usb1/periodic > > > while it's making that buzz? Where I'm assuming "usb1" is your EHCI, > > > and you've compiled with CONFIG_USB_DEBUG. > > > > > > - Dave > > > > > > > > > > Shiju > > > > > > > > > > > > On Wed, 9 Mar 2005 09:12:57 -0800, David Brownell <[EMAIL PROTECTED]> > > > > wrote: > > > > > On Wednesday 09 March 2005 1:17 am, Shiju Mathew wrote: > > > > > > Hi, > > > > > > When I connect the usb audio(CM108) to a USB 2.0 hub which inturn is > > > > > > connected to the system root hub, the audio quality is very bad. I > > > > > > hear a audible buzz . ... > > > > > > > > > > http://marc.theaimsgroup.com/?l=linux-usb-devel&m=111022243725297&w=2 > > > > > > > > > > has two patches to try. > > > > > > > > > > > > > > > > > > -- > > Regards, > > Shiju > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > _______________________________________________ > > linux-usb-devel@lists.sourceforge.net > > To unsubscribe, use the last form field at: > > https://lists.sourceforge.net/lists/listinfo/linux-usb-devel > > > -- Regards, Shiju ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
