From: Lars Melin <larsm17@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>, Bruno Haible <bruno@clisp.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Oliver Neukum <oneukum@suse.com>,
linux-usb@vger.kernel.org
Subject: Re: "SilverStone TS16" external SSD enclosing needs an UAS quirk
Date: Wed, 17 Jan 2024 13:25:21 +0700 [thread overview]
Message-ID: <fc14c873-04ee-43cd-8328-b4e5b03e0230@gmail.com> (raw)
In-Reply-To: <2024011630-convent-slouching-ce10@gregkh>
On 2024-01-16 21:13, Greg KH wrote:
> On Tue, Jan 16, 2024 at 12:35:46AM +0100, Bruno Haible wrote:
>> TL;DR
>> -----
>> In my experience, the "SilverStone TS16" external SSD enclosing
>> needs an UAS quirk
>> usb-storage.quirks=0bda:9210:u
>> as part of the kernel command line. I hope you can add it
>> to the file linux/drivers/usb/storage/unusual_uas.h .
>
> Can you create a patch for this so that you get credit for the making
> the fix?
>
> thanks,
>
> greg k-h
Replying to this since I did not get the original post.
0bda:9210 is a Realtek USB 3 to pcie chip used by umpteen
enclosure manufacturers.
I have got one from Orico and it works ok under both linux and MSWin but
it can be a bit finicky if it doesn't get enough power, it may for
instance work well with an earlier (slower) type of NVME SSD but not
with a later faster type unless you provide external power to it (usb
hub + power adapter).
Slowing down all RTL9120 already in the market with this quirk is in my
humble opinion not a realistic solutio.
tnx
/Lars
next prev parent reply other threads:[~2024-01-17 6:25 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 [this message]
2024-01-17 7:59 ` Bruno Haible
2024-01-17 14:11 ` [PATCH] uas: Disable UAS driver for Realtek RTL9210 M.2 NVME Adapters Bruno Haible
2024-01-17 14:53 ` "SilverStone TS16" external SSD enclosing needs an UAS quirk 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=fc14c873-04ee-43cd-8328-b4e5b03e0230@gmail.com \
--to=larsm17@gmail.com \
--cc=bruno@clisp.org \
--cc=gregkh@linuxfoundation.org \
--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.