From: "zhongling0719@126.com" <zhongling0719@126.com>
To: "Greg KH" <gregkh@linuxfoundation.org>,
"Juhyung Park" <qkrwngud825@gmail.com>
Cc: "stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"usb-storage@lists.one-eyed-alien.net"
<usb-storage@lists.one-eyed-alien.net>
Subject: Re: Re: [PATCH v6 2/3] usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
Date: Sat, 12 Nov 2022 15:45:36 +0800 [thread overview]
Message-ID: <2022111215445443712314@126.com> (raw)
In-Reply-To: Y2uDnUQKCDGzioJN@kroah.com
Hi:
This error not happend on all RTL9210,The uas blacklist only for on sale device(0x0bda, 0x9210).
Thanks!
zhongling0719@126.com
From: Greg KH
Date: 2022-11-09 18:40
To: Juhyung Park
CC: Hongling Zeng; stern; linux-usb; usb-storage; zhongling0719
Subject: Re: [PATCH v6 2/3] usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
On Mon, Oct 31, 2022 at 03:17:48PM +0900, Juhyung Park wrote:
> Hi,
>
> I'm speaking from my own experience but RTL9210 is arguably the most
> reliable NVMe-to-USB converter available.
>
> Compared to solutions from JMicron (multiple revisions) and ASMedia, RTL9210
> gave the lowest power consumption (from implementing proper power management
> commands) and the least headache.
>
> I personally own multiple enclosures and not one gave a single UAS error
> from multiple platforms (Android, Intel, AMD) for years, but with this
> commit now, it effectively disables UAS for all RTL9210 enclosures.
>
> Would it be possible to apply this quirk only to a specific firmware
> (range)? RTL9210 have a lot of possible firmware combinations: https://www.station-drivers.com/index.php/en/component/remository/Drivers/Realtek/NVMe-USB-3.1/lang,en-gb/
>
> RTL9210 was available since 2019 and the fact that this quirk came up this
> late leads me to believe that this is not a widespread issue and it'll be a
> shame if all of RTL9210s are blacklisted from UAS with Linux from now on :(
>
> If any additional information is required, please let me know.
Can you send a revert of this commit so that we can fix this up?
thanks,
greg k-h
next prev parent reply other threads:[~2022-11-12 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 2:49 [PATCH v6 2/3] usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS Hongling Zeng
2022-09-15 19:32 ` Alan Stern
[not found] ` <2fcdca5a-2deb-66ca-fd1d-c3ba719b19af@126.com>
2022-09-16 17:21 ` Alan Stern
2022-09-18 12:25 ` zhongling0719
2022-09-22 8:17 ` nana
2022-09-22 15:16 ` Alan Stern
2022-10-31 6:17 ` Juhyung Park
2022-11-09 10:40 ` Greg KH
2022-11-12 7:45 ` zhongling0719 [this message]
2022-11-12 7:56 ` Greg KH
2023-01-09 12:00 ` Juhyung Park
2023-01-09 11:58 ` Juhyung Park
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=2022111215445443712314@126.com \
--to=zhongling0719@126.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=qkrwngud825@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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.