drivers/usb/storage/unusual_uas.h | 7 +++++++ 1 file changed, 7 insertions(+)
The SanDisk Extreme Pro 55AF storage device(0781:55af) has poor compatibility with UAS drivers.
The logs:
[ 1.359859][ 0] [ T163] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 1.385708][ 0] [ T163] usb 2-1: New USB device found, idVendor=0781, idProduct=55af, bcdDevice=10.85
[ 1.385709][ 0] [ T163] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 1.385710][ 0] [ T163] usb 2-1: Product: Extreme Pro 55AF
[ 1.385711][ 0] [ T163] usb 2-1: Manufacturer: SanDisk
[ 1.385711][ 0] [ T163] usb 2-1: SerialNumber: 323234323935343030343636
[ 1.927603][ 0] [ T306] usbcore: registered new interface driver usb-storage
[ 1.940511][ 0] [ T306] scsi host3: uas
[ 1.940584][ 0] [ T306] usbcore: registered new interface driver uas
[ 1.940843][ 0] [ T188] scsi 3:0:0:0: Direct-Access SanDisk Extreme Pro 55AF 1085 PQ: 0 ANSI: 6
[ 1.941363][ 0] [ T188] scsi 3:0:0:1: Enclosure SanDisk SES Device 1085 PQ: 0 ANSI: 6
[ 1.941697][ 0] [ T188] sd 3:0:0:0: Attached scsi generic sg0 type 0
[ 1.941783][ 0] [ T188] scsi 3:0:0:1: Attached scsi generic sg1 type 13
[ 1.942296][ 0] [ T189] sd 3:0:0:0: [sda] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB)
[ 1.942373][ 0] [ T189] sd 3:0:0:0: [sda] Write Protect is off
[ 1.942374][ 0] [ T189] sd 3:0:0:0: [sda] Mode Sense: 37 00 10 00
[ 1.942534][ 0] [ T189] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 1.943586][ 0] [ T189] sd 3:0:0:0: [sda] Optimal transfer size 2097152 bytes
[ 1.976797][ 0] [ T189] sda: sda1
[ 1.977898][ 0] [ T189] sd 3:0:0:0: [sda] Attached SCSI disk
[ 1.980406][ 0] [ T267] scsi 3:0:0:1: Failed to get diagnostic page 0x1
[ 1.980408][ 0] [ T267] scsi 3:0:0:1: Failed to bind enclosure -19
[ 1.980414][ 0] [ T267] ses 3:0:0:1: Attached Enclosure device
[ 1.981068][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 data cmplt err -75 uas-tag 1 inflight: CMD
[ 1.981071][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00
[ 33.819186][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
[ 33.819188][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00
[ 33.843186][ 0] [ T309] scsi host3: uas_eh_device_reset_handler start
Device decriptor is below:
Bus 002 Device 003: ID 0781:55af SanDisk Corp. Extreme Pro 55AF
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.20
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0781 SanDisk Corp.
idProduct 0x55af
bcdDevice 10.85
iManufacturer 2 SanDisk
iProduct 3 Extreme Pro 55AF
iSerial 1 323234323935343030343636
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0079
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 896mA
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
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
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
MaxStreams 32
Data-in pipe (0x03)
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
MaxStreams 32
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
MaxStreams 32
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
Command pipe (0x01)
So ignore UAS driver for this device.
Signed-off-by: Jie Deng <dengjie03@kylinos.cn>
---
v2:
* According to the file modification rules (sort by VendorID
first, then by ProductID.) Add the newly added "UNUSUAL_DEV"
in the correct position.
v1:
* The newly added "UNUSUAL_DEV" was directly added to the end
without modifying the format according to the file.
---
drivers/usb/storage/unusual_uas.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/usb/storage/unusual_uas.h b/drivers/usb/storage/unusual_uas.h
index 1477e31d7763..6b1a08e2e724 100644
--- a/drivers/usb/storage/unusual_uas.h
+++ b/drivers/usb/storage/unusual_uas.h
@@ -52,6 +52,13 @@ UNUSUAL_DEV(0x059f, 0x1061, 0x0000, 0x9999,
USB_SC_DEVICE, USB_PR_DEVICE, NULL,
US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME),
+/* Reported-by: Jie Deng <dengjie03@kylinos.cn> */
+UNUSUAL_DEV(0x0781, 0x55af, 0x0000, 0x9999,
+ "SanDisk",
+ "Extreme Pro 55AF",
+ USB_SC_DEVICE, USB_PR_DEVICE, NULL,
+ US_FL_IGNORE_UAS),
+
/* Reported-by: Zhihong Zhou <zhouzhihong@greatwall.com.cn> */
UNUSUAL_DEV(0x0781, 0x55e8, 0x0000, 0x9999,
"SanDisk",
--
2.25.1On Mon, Jul 07, 2025 at 02:25:07PM +0800, Jie Deng wrote: > The SanDisk Extreme Pro 55AF storage device(0781:55af) has poor compatibility with UAS drivers. > The logs: > [ 1.359859][ 0] [ T163] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd Nit, the [] stuff should all be removed, it's not relevant, right? > [ 1.385708][ 0] [ T163] usb 2-1: New USB device found, idVendor=0781, idProduct=55af, bcdDevice=10.85 > [ 1.385709][ 0] [ T163] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 > [ 1.385710][ 0] [ T163] usb 2-1: Product: Extreme Pro 55AF > [ 1.385711][ 0] [ T163] usb 2-1: Manufacturer: SanDisk > [ 1.385711][ 0] [ T163] usb 2-1: SerialNumber: 323234323935343030343636 > [ 1.927603][ 0] [ T306] usbcore: registered new interface driver usb-storage > [ 1.940511][ 0] [ T306] scsi host3: uas > [ 1.940584][ 0] [ T306] usbcore: registered new interface driver uas > [ 1.940843][ 0] [ T188] scsi 3:0:0:0: Direct-Access SanDisk Extreme Pro 55AF 1085 PQ: 0 ANSI: 6 > [ 1.941363][ 0] [ T188] scsi 3:0:0:1: Enclosure SanDisk SES Device 1085 PQ: 0 ANSI: 6 > [ 1.941697][ 0] [ T188] sd 3:0:0:0: Attached scsi generic sg0 type 0 > [ 1.941783][ 0] [ T188] scsi 3:0:0:1: Attached scsi generic sg1 type 13 > [ 1.942296][ 0] [ T189] sd 3:0:0:0: [sda] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB) > [ 1.942373][ 0] [ T189] sd 3:0:0:0: [sda] Write Protect is off > [ 1.942374][ 0] [ T189] sd 3:0:0:0: [sda] Mode Sense: 37 00 10 00 > [ 1.942534][ 0] [ T189] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA > [ 1.943586][ 0] [ T189] sd 3:0:0:0: [sda] Optimal transfer size 2097152 bytes > [ 1.976797][ 0] [ T189] sda: sda1 > [ 1.977898][ 0] [ T189] sd 3:0:0:0: [sda] Attached SCSI disk > [ 1.980406][ 0] [ T267] scsi 3:0:0:1: Failed to get diagnostic page 0x1 > [ 1.980408][ 0] [ T267] scsi 3:0:0:1: Failed to bind enclosure -19 > [ 1.980414][ 0] [ T267] ses 3:0:0:1: Attached Enclosure device > [ 1.981068][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 data cmplt err -75 uas-tag 1 inflight: CMD > [ 1.981071][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00 > [ 33.819186][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD > [ 33.819188][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00 > [ 33.843186][ 0] [ T309] scsi host3: uas_eh_device_reset_handler start So new devices are being made that can not handle UAS? Are you sure there's not some other quirk that could be used here instead? How does this device work on other operating systems with the UAS drivers there? thanks, greg k-h
在 2025/7/7 16:49, Greg KH 写道: > On Mon, Jul 07, 2025 at 02:25:07PM +0800, Jie Deng wrote: >> The SanDisk Extreme Pro 55AF storage device(0781:55af) has poor compatibility with UAS drivers. >> The logs: >> [ 1.359859][ 0] [ T163] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd > Nit, the [] stuff should all be removed, it's not relevant, right? > >> [ 1.385708][ 0] [ T163] usb 2-1: New USB device found, idVendor=0781, idProduct=55af, bcdDevice=10.85 >> [ 1.385709][ 0] [ T163] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 >> [ 1.385710][ 0] [ T163] usb 2-1: Product: Extreme Pro 55AF >> [ 1.385711][ 0] [ T163] usb 2-1: Manufacturer: SanDisk >> [ 1.385711][ 0] [ T163] usb 2-1: SerialNumber: 323234323935343030343636 >> [ 1.927603][ 0] [ T306] usbcore: registered new interface driver usb-storage >> [ 1.940511][ 0] [ T306] scsi host3: uas >> [ 1.940584][ 0] [ T306] usbcore: registered new interface driver uas >> [ 1.940843][ 0] [ T188] scsi 3:0:0:0: Direct-Access SanDisk Extreme Pro 55AF 1085 PQ: 0 ANSI: 6 >> [ 1.941363][ 0] [ T188] scsi 3:0:0:1: Enclosure SanDisk SES Device 1085 PQ: 0 ANSI: 6 >> [ 1.941697][ 0] [ T188] sd 3:0:0:0: Attached scsi generic sg0 type 0 >> [ 1.941783][ 0] [ T188] scsi 3:0:0:1: Attached scsi generic sg1 type 13 >> [ 1.942296][ 0] [ T189] sd 3:0:0:0: [sda] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB) >> [ 1.942373][ 0] [ T189] sd 3:0:0:0: [sda] Write Protect is off >> [ 1.942374][ 0] [ T189] sd 3:0:0:0: [sda] Mode Sense: 37 00 10 00 >> [ 1.942534][ 0] [ T189] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA >> [ 1.943586][ 0] [ T189] sd 3:0:0:0: [sda] Optimal transfer size 2097152 bytes >> [ 1.976797][ 0] [ T189] sda: sda1 >> [ 1.977898][ 0] [ T189] sd 3:0:0:0: [sda] Attached SCSI disk >> [ 1.980406][ 0] [ T267] scsi 3:0:0:1: Failed to get diagnostic page 0x1 >> [ 1.980408][ 0] [ T267] scsi 3:0:0:1: Failed to bind enclosure -19 >> [ 1.980414][ 0] [ T267] ses 3:0:0:1: Attached Enclosure device >> [ 1.981068][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 data cmplt err -75 uas-tag 1 inflight: CMD >> [ 1.981071][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00 >> [ 33.819186][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD >> [ 33.819188][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00 >> [ 33.843186][ 0] [ T309] scsi host3: uas_eh_device_reset_handler start > So new devices are being made that can not handle UAS? Are you sure > there's not some other quirk that could be used here instead? How does > this device work on other operating systems with the UAS drivers there? > > thanks, > > greg k-h Thank you for your reply. 1. The information within [] is redundant and should be removed 2. Regarding your question, before submitting the patch, I conducted the following tests: 1) linux + x86: The SanDisk Extreme Pro 55AF device can be recognized normally when using the uas driver. USB controller model (VendorID: 1D94, DeviceID: 145F,Chengdu Haiguang IC Design Co., Ltd.USB 3.0 Host controller) 2) linux + arm64: The SanDisk Extreme Pro 55AF device will report an error when using the uas driver and the driver cannot be loaded. USB Controller model (Vendor ID: 1912, Device ID: 0014,uPD720201 USB 3.0 Host Controller). 3) linux + arm64: Add the parameter "USB-storage.quirks =0781:55af:u" in grub. The SanDisk Extreme Pro 55AF device runs the usb storage driver without any error and can be recognized normally.
On Tue, Jul 08, 2025 at 01:55:47PM +0800, Jie Deng wrote: > 2. Regarding your question, before submitting the patch, > I conducted the following tests: > 1) linux + x86: The SanDisk Extreme Pro 55AF device can be recognized > normally when using the uas driver. USB controller model (VendorID: > 1D94, DeviceID: 145F,Chengdu Haiguang IC Design Co., Ltd.USB 3.0 Host > controller) So it all works, great! > 2) linux + arm64: The SanDisk Extreme Pro 55AF device will report an error > when > using the uas driver and the driver cannot be loaded. USB Controller model > (Vendor ID: 1912, Device ID: 0014,uPD720201 USB 3.0 Host Controller). Ok, that sounds like an arm64 issue we should resolve. Why can the driver not be loaded at all? What happens? > 3) linux + arm64: Add the parameter "USB-storage.quirks =0781:55af:u" in > grub. > The SanDisk Extreme Pro 55AF device runs the usb storage driver without any > error > and can be recognized normally. Let's track down and fix the arm64 issue here please, and not paper over it by saying that this whole device will not work well on all arches. thakns, greg k-h
On Mon, Jul 07, 2025 at 02:25:07PM +0800, Jie Deng wrote: > The SanDisk Extreme Pro 55AF storage device(0781:55af) has poor compatibility with UAS drivers. > The logs: > [ 1.359859][ 0] [ T163] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd > [ 1.385708][ 0] [ T163] usb 2-1: New USB device found, idVendor=0781, idProduct=55af, bcdDevice=10.85 > [ 1.385709][ 0] [ T163] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 > [ 1.385710][ 0] [ T163] usb 2-1: Product: Extreme Pro 55AF > [ 1.385711][ 0] [ T163] usb 2-1: Manufacturer: SanDisk > [ 1.385711][ 0] [ T163] usb 2-1: SerialNumber: 323234323935343030343636 > [ 1.927603][ 0] [ T306] usbcore: registered new interface driver usb-storage > [ 1.940511][ 0] [ T306] scsi host3: uas > [ 1.940584][ 0] [ T306] usbcore: registered new interface driver uas > [ 1.940843][ 0] [ T188] scsi 3:0:0:0: Direct-Access SanDisk Extreme Pro 55AF 1085 PQ: 0 ANSI: 6 > [ 1.941363][ 0] [ T188] scsi 3:0:0:1: Enclosure SanDisk SES Device 1085 PQ: 0 ANSI: 6 > [ 1.941697][ 0] [ T188] sd 3:0:0:0: Attached scsi generic sg0 type 0 > [ 1.941783][ 0] [ T188] scsi 3:0:0:1: Attached scsi generic sg1 type 13 > [ 1.942296][ 0] [ T189] sd 3:0:0:0: [sda] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB) > [ 1.942373][ 0] [ T189] sd 3:0:0:0: [sda] Write Protect is off > [ 1.942374][ 0] [ T189] sd 3:0:0:0: [sda] Mode Sense: 37 00 10 00 > [ 1.942534][ 0] [ T189] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA > [ 1.943586][ 0] [ T189] sd 3:0:0:0: [sda] Optimal transfer size 2097152 bytes > [ 1.976797][ 0] [ T189] sda: sda1 > [ 1.977898][ 0] [ T189] sd 3:0:0:0: [sda] Attached SCSI disk > [ 1.980406][ 0] [ T267] scsi 3:0:0:1: Failed to get diagnostic page 0x1 > [ 1.980408][ 0] [ T267] scsi 3:0:0:1: Failed to bind enclosure -19 > [ 1.980414][ 0] [ T267] ses 3:0:0:1: Attached Enclosure device > [ 1.981068][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 data cmplt err -75 uas-tag 1 inflight: CMD > [ 1.981071][ 0] [ C0] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00 > [ 33.819186][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD > [ 33.819188][ 0] [ T188] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00 > [ 33.843186][ 0] [ T309] scsi host3: uas_eh_device_reset_handler start > > Device decriptor is below: > Bus 002 Device 003: ID 0781:55af SanDisk Corp. Extreme Pro 55AF > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 3.20 > bDeviceClass 0 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 9 > idVendor 0x0781 SanDisk Corp. > idProduct 0x55af > bcdDevice 10.85 > iManufacturer 2 SanDisk > iProduct 3 Extreme Pro 55AF > iSerial 1 323234323935343030343636 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 0x0079 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0x80 > (Bus Powered) > MaxPower 896mA > 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 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 1 > bNumEndpoints 4 > bInterfaceClass 8 Mass Storage > bInterfaceSubClass 6 SCSI > bInterfaceProtocol 98 > 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 > MaxStreams 32 > Data-in pipe (0x03) > 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 > MaxStreams 32 > Data-out pipe (0x04) > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0400 1x 1024 bytes > bInterval 0 > bMaxBurst 15 > MaxStreams 32 > Status pipe (0x02) > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x04 EP 4 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0400 1x 1024 bytes > bInterval 0 > bMaxBurst 0 > Command pipe (0x01) > > So ignore UAS driver for this device. > > Signed-off-by: Jie Deng <dengjie03@kylinos.cn> > --- > v2: > * According to the file modification rules (sort by VendorID > first, then by ProductID.) Add the newly added "UNUSUAL_DEV" > in the correct position. > v1: > * The newly added "UNUSUAL_DEV" was directly added to the end > without modifying the format according to the file. > > --- > drivers/usb/storage/unusual_uas.h | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/drivers/usb/storage/unusual_uas.h b/drivers/usb/storage/unusual_uas.h > index 1477e31d7763..6b1a08e2e724 100644 > --- a/drivers/usb/storage/unusual_uas.h > +++ b/drivers/usb/storage/unusual_uas.h > @@ -52,6 +52,13 @@ UNUSUAL_DEV(0x059f, 0x1061, 0x0000, 0x9999, > USB_SC_DEVICE, USB_PR_DEVICE, NULL, > US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME), > > +/* Reported-by: Jie Deng <dengjie03@kylinos.cn> */ > +UNUSUAL_DEV(0x0781, 0x55af, 0x0000, 0x9999, > + "SanDisk", > + "Extreme Pro 55AF", > + USB_SC_DEVICE, USB_PR_DEVICE, NULL, > + US_FL_IGNORE_UAS), > + > /* Reported-by: Zhihong Zhou <zhouzhihong@greatwall.com.cn> */ > UNUSUAL_DEV(0x0781, 0x55e8, 0x0000, 0x9999, > "SanDisk", > -- > 2.25.1 Why is there two "v2" patches sent here? Shouldn't this be "v3"? confused, greg k-h
在 2025/7/7 16:47, Greg KH 写道: > > So ignore UAS driver for this device. > > > > Signed-off-by: Jie Deng <dengjie03@kylinos.cn> > > --- > > v2: > > * According to the file modification rules (sort by VendorID > > first, then by ProductID.) Add the newly added "UNUSUAL_DEV" > > in the correct position. > > v1: > > * The newly added "UNUSUAL_DEV" was directly added to the end > > without modifying the format according to the file. > > > > --- > > drivers/usb/storage/unusual_uas.h | 7 +++++++ > > 1 file changed, 7 insertions(+) > > > > diff --git a/drivers/usb/storage/unusual_uas.h b/drivers/usb/storage/unusual_uas.h > > index 1477e31d7763..6b1a08e2e724 100644 > > --- a/drivers/usb/storage/unusual_uas.h > > +++ b/drivers/usb/storage/unusual_uas.h > > @@ -52,6 +52,13 @@ UNUSUAL_DEV(0x059f, 0x1061, 0x0000, 0x9999, > > USB_SC_DEVICE, USB_PR_DEVICE, NULL, > > US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME), > > > > +/* Reported-by: Jie Deng <dengjie03@kylinos.cn> */ > > +UNUSUAL_DEV(0x0781, 0x55af, 0x0000, 0x9999, > > + "SanDisk", > > + "Extreme Pro 55AF", > > + USB_SC_DEVICE, USB_PR_DEVICE, NULL, > > + US_FL_IGNORE_UAS), > > + > > /* Reported-by: Zhihong Zhou <zhouzhihong@greatwall.com.cn> */ > > UNUSUAL_DEV(0x0781, 0x55e8, 0x0000, 0x9999, > > "SanDisk", > > -- > > 2.25.1 > > Why is there two "v2" patches sent here? Shouldn't this be "v3"? > > confused, > > greg k-h > The first sent V2 patch was missing the description of the differences between V1 and V2 patches. The V2 patch sent for the second time only adds a description of the differences from the V1 patch compared to the V2 patch sent for the first time. There is no modification to the code. So it is rashly believed that it does not need to be defined as a V3 patch.
On Mon, Jul 07, 2025 at 05:52:31PM +0800, Jie Deng wrote: > > 在 2025/7/7 16:47, Greg KH 写道: > > > So ignore UAS driver for this device. > > > > Signed-off-by: Jie Deng <dengjie03@kylinos.cn> > > > --- > > > v2: > > > * According to the file modification rules (sort by VendorID > > > first, then by ProductID.) Add the newly added "UNUSUAL_DEV" > in the > > correct position. > > > v1: > > > * The newly added "UNUSUAL_DEV" was directly added to the end > > > without modifying the format according to the file. > > > > --- > > > drivers/usb/storage/unusual_uas.h | 7 +++++++ > > > 1 file changed, 7 insertions(+) > > > > diff --git a/drivers/usb/storage/unusual_uas.h > > b/drivers/usb/storage/unusual_uas.h > > > index 1477e31d7763..6b1a08e2e724 100644 > > > --- a/drivers/usb/storage/unusual_uas.h > > > +++ b/drivers/usb/storage/unusual_uas.h > > > @@ -52,6 +52,13 @@ UNUSUAL_DEV(0x059f, 0x1061, 0x0000, 0x9999, > > > USB_SC_DEVICE, USB_PR_DEVICE, NULL, > > > US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME), > > > > +/* Reported-by: Jie Deng <dengjie03@kylinos.cn> */ > > > +UNUSUAL_DEV(0x0781, 0x55af, 0x0000, 0x9999, > > > + "SanDisk", > > > + "Extreme Pro 55AF", > > > + USB_SC_DEVICE, USB_PR_DEVICE, NULL, > > > + US_FL_IGNORE_UAS), > > > + > > > /* Reported-by: Zhihong Zhou <zhouzhihong@greatwall.com.cn> */ > > > UNUSUAL_DEV(0x0781, 0x55e8, 0x0000, 0x9999, > > > "SanDisk", > > > -- > 2.25.1 > > > > Why is there two "v2" patches sent here? Shouldn't this be "v3"? > > > > confused, > > > > greg k-h > > > The first sent V2 patch was missing the description of the > differences between V1 and V2 patches. The V2 patch sent for > the second time only adds a description of the differences > from the V1 patch compared to the V2 patch sent for the first time. > There is no modification to the code. So it is rashly believed > that it does not need to be defined as a V3 patch. > Think about what you would do if you got sent 2 "v2" patches? :) Remember, some of us get hundreds/thousands of emails to handle a day, please make it very obvious what to do here. thanks, greg k-h
在 2025/7/8 15:32, Greg KH 写道: > On Mon, Jul 07, 2025 at 05:52:31PM +0800, Jie Deng wrote: >> 在 2025/7/7 16:47, Greg KH 写道: >>> > So ignore UAS driver for this device. >>>>> Signed-off-by: Jie Deng <dengjie03@kylinos.cn> >>>> --- >>>> v2: >>>> * According to the file modification rules (sort by VendorID > >>> first, then by ProductID.) Add the newly added "UNUSUAL_DEV" > in the >>> correct position. >>>> v1: >>>> * The newly added "UNUSUAL_DEV" was directly added to the end > >>> without modifying the format according to the file. >>>>> --- >>>> drivers/usb/storage/unusual_uas.h | 7 +++++++ >>>> 1 file changed, 7 insertions(+) >>>>> diff --git a/drivers/usb/storage/unusual_uas.h >>> b/drivers/usb/storage/unusual_uas.h >>>> index 1477e31d7763..6b1a08e2e724 100644 >>>> --- a/drivers/usb/storage/unusual_uas.h >>>> +++ b/drivers/usb/storage/unusual_uas.h >>>> @@ -52,6 +52,13 @@ UNUSUAL_DEV(0x059f, 0x1061, 0x0000, 0x9999, >>>> USB_SC_DEVICE, USB_PR_DEVICE, NULL, >>>> US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME), >>>> > +/* Reported-by: Jie Deng <dengjie03@kylinos.cn> */ >>>> +UNUSUAL_DEV(0x0781, 0x55af, 0x0000, 0x9999, >>>> + "SanDisk", >>>> + "Extreme Pro 55AF", >>>> + USB_SC_DEVICE, USB_PR_DEVICE, NULL, >>>> + US_FL_IGNORE_UAS), >>>> + >>>> /* Reported-by: Zhihong Zhou <zhouzhihong@greatwall.com.cn> */ >>>> UNUSUAL_DEV(0x0781, 0x55e8, 0x0000, 0x9999, >>>> "SanDisk", >>>> -- > 2.25.1 >>> Why is there two "v2" patches sent here? Shouldn't this be "v3"? >>> >>> confused, >>> >>> greg k-h >>> >> The first sent V2 patch was missing the description of the >> differences between V1 and V2 patches. The V2 patch sent for >> the second time only adds a description of the differences >> from the V1 patch compared to the V2 patch sent for the first time. >> There is no modification to the code. So it is rashly believed >> that it does not need to be defined as a V3 patch. >> > Think about what you would do if you got sent 2 "v2" patches? :) > > Remember, some of us get hundreds/thousands of emails to handle a day, > please make it very obvious what to do here. > > thanks, > > greg k-h I'm very sorry. I'll pay attention when submitting patches later
© 2016 - 2025 Red Hat, Inc.