Re: [PATCH 1/5] USB: Add parsing of SuperSpeed endpoint companion descriptor.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Apr 23, 2010 at 03:05:14PM -0700, Sarah Sharp wrote:
> On Fri, Apr 23, 2010 at 05:34:14PM -0400, Alan Stern wrote:
> > On Fri, 23 Apr 2010, Sarah Sharp wrote:
> > 
> > > > Does this look okay to you?  I don't have any way to test it.
> > > 
> > > Yes and no.  Everything seems to behave properly with all the USB
> > > devices I have; the I can read and write to the USB 3.0 hard drives,
> > > etc.  (The one thing I don't have is a USB 3.0 device that has
> > > descriptors between the SuperSpeed Endpoint Companion Descriptor and the
> > > next Endpoint Descriptor, like a UAS device would have).
> > > 
> > > However, some devices are missing from the lsusb output, which is very
> > > strange.  Specifically, the roothub is always missing, and any hubs
> > > directly connected to it disappear after a device has been plugged into
> > > them.  Hubs further up the tree do not disappear from the lsusb output.
> > > I think this might be related to the fact that the roothub doesn't have
> > > a SuperSpeed Endpoint Companion Descriptor.
> > 
> > Very weird indeed.  What shows up in /sys/kernel/debug/usb/devices?
> 
> The USB devices show up fine there.  Here's with the roothub and just a HS hub:
> 
> sarah@xanatos:~$ lsusb
> Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 003: ID 0a5c:2145 Broadcom Corp. 
> Bus 003 Device 002: ID 08ff:2810 AuthenTec, Inc. 
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> sarah@xanatos:~$ ls /sys/bus/usb/devices/
> 1-0:1.0  3-0:1.0  3-1:1.0  3-2:1.0  3-2:1.2  4-0:1.0  6-0:1.0  8-0:1.0  usb1  usb3  usb5  usb7  usb9
> 2-0:1.0  3-1      3-2      3-2:1.1  3-2:1.3  5-0:1.0  7-0:1.0  9-0:1.0  usb2  usb4  usb6  usb8
> sarah@xanatos:~$ ls /sys/bus/usb/devices/usb9/
> 9-0:1.0             avoid_reset_quirk    bDeviceProtocol  bMaxPower           configuration  devpath    idVendor      product  speed      version
> 9-3                 bcdDevice            bDeviceSubClass  bNumConfigurations  descriptors    driver     manufacturer  quirks   subsystem
> authorized          bConfigurationValue  bmAttributes     bNumInterfaces      dev            ep_00      maxchild      remove   uevent
> authorized_default  bDeviceClass         bMaxPacketSize0  busnum              devnum         idProduct  power         serial   urbnum
> 
> > If that looks all right then maybe the problem is somehow in lsusb.
> > You can find out what lsusb is up to by doing
> >
> > 	echo 1 >/sys/module/usbcore/parameters/usbfs_snoop
> > 
> > before starting the program and then looking at the dmesg log after it 
> > runs.
> 
> Here's the output from dmesg when I run lsusb after executing that
> command:

Can you clone and build and run the program at:
	git://github.com/gregkh/lsusb.git
and see if that shows anything different?

It only looks at sysfs, not usbfs, and uses libudev to enumerate USB
devices.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux