Hi Greg Yes Orico is a kind of crap, but it is not so easy to find those kind of devices. My concern is that we may see one of this crappy implementation of device, such that it actually supports perfectly UASP but they "forgot" to set something in the firmware, maybe just the capability My question was more to see if there is already something in the USB-STORAGE that allow it or if we may endup in another "quirks" for addressing these problem Honestly, with all the concern I can have about Orico, if they advice the device as UASP capable and the chipset support it, I think it should really support it in the end The device is this one: http://www.orico.cc/goods.php?id=6538 Is it possible that the USB host (in my case it is a modern Intel USB 3.1 controller from an Atom embedded PC) play a role in this? I have another Orico multy bay, older, same JMS567 chipset that show up as UASP capable 2018-03-16 15:04 GMT+01:00 Greg KH <greg@xxxxxxxxx>: > On Fri, Mar 16, 2018 at 02:10:43PM +0100, Menion wrote: >> Hi all >> I have in my hands a multi bay SATA enclosure, with some unidentified >> SATA multiport but using the JMicron JMS567 USB to SATA bridge. >> This bridge is known to support UASP but in this particular >> implementation, due to something weird/buggy (most probably the >> firmware) doesn't who up as UASP capable, in fact a lsusb -t shows no >> bInterfaceProtocol 98: >> >> Bus 002 Device 003: ID 152d:0567 JMicron Technology Corp. / JMicron >> USA Technology Corp. JMS567 SATA 6Gb/s bridge >> Device Descriptor: >> bLength 18 >> bDescriptorType 1 >> bcdUSB 3.00 >> bDeviceClass 0 (Defined at Interface level) >> bDeviceSubClass 0 >> bDeviceProtocol 0 >> bMaxPacketSize0 9 >> idVendor 0x152d JMicron Technology Corp. / JMicron USA >> Technology Corp. >> idProduct 0x0567 JMS567 SATA 6Gb/s bridge >> bcdDevice 3.24 >> iManufacturer 1 JMicron >> iProduct 2 USB to ATA/ATAPI Bridge >> iSerial 3 0123456789ABCDEF >> bNumConfigurations 1 >> Configuration Descriptor: >> bLength 9 >> bDescriptorType 2 >> wTotalLength 44 >> bNumInterfaces 1 >> bConfigurationValue 1 >> iConfiguration 0 >> bmAttributes 0xc0 >> Self Powered >> MaxPower 2mA >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 0 >> bAlternateSetting 0 >> bNumEndpoints 2 >> bInterfaceClass 8 Mass Storage >> bInterfaceSubClass 6 SCSI >> bInterfaceProtocol 80 Bulk-Only >> iInterface 0 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x81 EP 1 IN >> bmAttributes 2 >> Transfer Type Bulk >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0400 1x 1024 bytes >> bInterval 0 >> bMaxBurst 15 >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x02 EP 2 OUT >> bmAttributes 2 >> Transfer Type Bulk >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0400 1x 1024 bytes >> bInterval 0 >> bMaxBurst 15 >> Binary Object Store Descriptor: >> bLength 5 >> bDescriptorType 15 >> wTotalLength 22 >> bNumDeviceCaps 2 >> USB 2.0 Extension Device Capability: >> bLength 7 >> bDescriptorType 16 >> bDevCapabilityType 2 >> bmAttributes 0x00000f0e >> Link Power Management (LPM) Supported >> SuperSpeed USB Device Capability: >> bLength 10 >> bDescriptorType 16 >> bDevCapabilityType 3 >> bmAttributes 0x00 >> wSpeedsSupported 0x000e >> Device can operate at Full Speed (12Mbps) >> Device can operate at High Speed (480Mbps) >> Device can operate at SuperSpeed (5Gbps) >> bFunctionalitySupport 1 >> Lowest fully-functional device speed is Full Speed (12Mbps) >> bU1DevExitLat 10 micro seconds >> bU2DevExitLat 32 micro seconds >> Device Status: 0x0001 >> Self Powered >> >> The vendor, Orico, claims explicitly that the enclosure shall support >> UASP. But without the bInterfaceProtocol 98 the device is not bind to >> UAS driver. So the question is: is there a way to forcibly bind a >> device to UAS? > > If the firmware does not support it, as it shows here it does not, no, > there is no way to do that, sorry. I suggest going and buying a better > device :) > > sorry, > > 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
