public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jie Deng <dengjie03@kylinos.cn>
Cc: stern@rowland.harvard.edu, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net
Subject: Re: [PATCH v2] usb: storage: Ignore UAS driver for SanDisk Extreme Pro 55AF storage device
Date: Tue, 8 Jul 2025 09:33:18 +0200	[thread overview]
Message-ID: <2025070810-nintendo-congenial-95d4@gregkh> (raw)
In-Reply-To: <4bac2d53-0e5b-437e-92bc-12921a8efd8d@kylinos.cn>

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

  reply	other threads:[~2025-07-08  7:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03  9:29 [PATCH] usb: storage: Ignore UAS driver for SanDisk Extreme Pro 55AF storage device Jie Deng
2025-07-03 10:01 ` Greg KH
2025-07-04  6:11   ` [PATCH v2] " Jie Deng
2025-07-04  8:24     ` Greg KH
2025-07-07  6:25       ` Jie Deng
2025-07-07  8:47         ` Greg KH
2025-07-07  9:52           ` Jie Deng
2025-07-08  7:32             ` Greg KH
2025-07-09  3:13               ` Jie Deng
2025-07-07  8:49         ` Greg KH
2025-07-08  5:55           ` Jie Deng
2025-07-08  7:33             ` Greg KH [this message]
     [not found]               ` <92f1e73f-5814-4e01-98b6-1c9c0b87f903@kylinos.cn>
2025-07-09  6:21                 ` Greg KH
2025-07-10  6:28                   ` Jie Deng
2025-07-04  7:39   ` [PATCH] " Jie Deng

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=2025070810-nintendo-congenial-95d4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dengjie03@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox