Linux USB
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Johan Gill <johan.gill@bahnhof.se>
Cc: linux-usb@vger.kernel.org
Subject: Re: UAS peripheral with unrecognized TRIM support
Date: Sun, 29 Mar 2026 08:21:49 +0200	[thread overview]
Message-ID: <2026032920-enforcer-saxophone-7707@gregkh> (raw)
In-Reply-To: <1717beab-848b-4927-8fa5-26fb5ae05495@bahnhof.se>

On Sat, Mar 28, 2026 at 05:23:48PM +0100, Johan Gill wrote:
> Hi, I have tested running Linux on the StarTech USB312SAT3CB USB 3.1 -> SATA
> adapter. It's a more stable UAS implementation than my previous adapter but
> the device is not recognized as supporting TRIM out of the box (kernel
> 6.19.9). The technical specifications at
> https://www.startech.com/en-se/hdd/usb312sat3cb indicate that TRIM is
> supported, so I enabled it by setting ATTR{provisioning_mode}="unmap" in a
> udev rule and then fstrim indeed seems to work when I run it. The
> specification claims that it uses ASMedia ASM235CM, but the device uses the
> StarTech vendor id and identifies as 14b0:0207.
> 
> It would be nice to have the adapter recognized as more capable out of the
> box. Should I aim at patching drivers/usb/storage/unusual_uas.h?

Isn't that a scsi issue, not a USB/UAS issue to be reporting that value
properly?  That sysfs attribute comes from the storage portion of the
kernel, not the USB portion.

thanks,

greg k-h

  reply	other threads:[~2026-03-29  6:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-28 16:23 UAS peripheral with unrecognized TRIM support Johan Gill
2026-03-29  6:21 ` Greg KH [this message]
2026-03-30 12:17 ` Oliver Neukum

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=2026032920-enforcer-saxophone-7707@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=johan.gill@bahnhof.se \
    --cc=linux-usb@vger.kernel.org \
    /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