All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bruno@clisp.org
Cc: gregkh@linuxfoundation.org, larsm17@gmail.com,
	linux-usb@vger.kernel.org, oneukum@suse.com,
	stern@rowland.harvard.edu
Subject: [PATCH] uas: Disable UAS driver for Realtek RTL9210 M.2 NVME Adapters
Date: Wed, 17 Jan 2024 15:11:32 +0100	[thread overview]
Message-ID: <20240117141132.1023457-1-bruno@clisp.org> (raw)
In-Reply-To: <2270283.o7ts2hSHzF@nimes>

Various products that make use of the Realtek RTL9210 M.2 NVME Adapter:
  - SilverStone TS16
  - Sabrent NVMe M.2 enclosure (Model EC-SNVE)
  - UnionSine Dual Protocol M2 NVMe to USB 3.1
malfunction when the UAS driver is used. At least for the
SilverStone TS16, it works fine when the usb-storage driver is used.

In my case, the SilverStone TS16 is identified by this output of
"lsusb -v":
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.20
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         9
  idVendor           0x0bda Realtek Semiconductor Corp.
  idProduct          0x9210 RTL9210 M.2 NVME Adapter
  bcdDevice           20.01
  iManufacturer           1 Realtek
  iProduct                2 USB 3.1 Storage Device
  iSerial                 3 221010010470

Signed-off-by: Bruno Haible <bruno@clisp.org>
Link: https://lore.kernel.org/linux-usb/2270283.o7ts2hSHzF@nimes/
---
 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 1f8c9b16a0fb..5287c7a446f1 100644
--- a/drivers/usb/storage/unusual_uas.h
+++ b/drivers/usb/storage/unusual_uas.h
@@ -83,6 +83,13 @@ UNUSUAL_DEV(0x0bc2, 0x331a, 0x0000, 0x9999,
 		USB_SC_DEVICE, USB_PR_DEVICE, NULL,
 		US_FL_NO_REPORT_LUNS),
 
+/* Reported-by: Bruno Haible <bruno@clisp.org> */
+UNUSUAL_DEV(0x0bda, 0x9210, 0x0000, 0x9999,
+		"Realtek",
+		"USB 3.1 Storage Device",
+		USB_SC_DEVICE, USB_PR_DEVICE, NULL,
+		US_FL_IGNORE_UAS),
+
 /* Reported-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> */
 UNUSUAL_DEV(0x13fd, 0x3940, 0x0000, 0x9999,
 		"Initio Corporation",
-- 
2.34.1


  reply	other threads:[~2024-01-17 14:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 23:35 "SilverStone TS16" external SSD enclosing needs an UAS quirk Bruno Haible
2024-01-16 14:13 ` Greg KH
2024-01-17  6:25   ` Lars Melin
2024-01-17  7:59     ` Bruno Haible
2024-01-17 14:11       ` Bruno Haible [this message]
2024-01-17 14:53       ` Alan Stern
2024-01-17 15:56         ` Bruno Haible
2024-01-17 18:39           ` Alan Stern
2024-01-17 16:41       ` Lars Melin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240117141132.1023457-1-bruno@clisp.org \
    --to=bruno@clisp.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=larsm17@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.