Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Thierry Vignaud <tvignaud@redhat.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: libata-core: Add NOLPM/NONCQ/1.5Gbps quirk for PNY 1TB SATA SSD
Date: Sat, 7 Nov 2026 15:06:52 +0100	[thread overview]
Message-ID: <au8wfDKEh9Nzt3D0@ryzen> (raw)
In-Reply-To: <20261028145535.623209-1-tvignaud@redhat.com>

On Wed, Oct 28, 2026 at 03:54:34PM +0100, Thierry Vignaud wrote:
> Without that, I get the errors below.
> For a year, I workaround it by disabling NCQ & reducing the speed by
> booting with "libata.force=1:3.0Gbps,1:noncq".
> It tried out disabling LPM only but I was still able to see errors.

The body should be readable without the subject, so please
rephrase "Without that,".


>
> Related: bko#222187

If you want to reference this, use the Link or Closes tag, e.g.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=222187

See:
https://docs.kernel.org/process/submitting-patches.html


> 
> v3:
> - add firmware revision check
> v2:
> - remove firmware revision from SSD name
> - drop speed to 1.5Gbs (as there's no 3.0Gbps quirk)
> - disable NCQ altogether (else we still see the errors from times to
>   times)

The changelog should be after the "---" line, before the diffstat, see e.g.:
https://lore.kernel.org/linux-ide/179405688421.943559.6118296661484264171.b4-ty@kernel.org/T/#t


The patch is missing v3 in the subject, so right now it has the same subject
as the previous patches, which is incorrectly putting all versions is the same
thread:
https://lore.kernel.org/linux-ide/CAHSMvrFXEnsLKF_BSYWz=V=ht6++RocuHJO0tkhUmPcHHvXp5A@mail.gmail.com/T/#t

You need to generate it using e.g.:

$ git format-patch -v 3

Which will generate the proper subject.


> ---
>  drivers/ata/libata-core.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index dadcaf9ff462..cde9d367c20f 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -4398,6 +4398,13 @@ static const struct ata_dev_quirks_entry __ata_dev_quirks[] = {
>  	/* PNY CS900 (Phison PS3111-S11, DRAM-less) drops the link on DIPM */
>  	{ "PNY CS900 1TB SSD",		NULL,	ATA_QUIRK_NOLPM },
>  
> +	/* PNY CS900 (variant) drops the link on DIPM and NCQ
> +	 * This covers only the 1TB variant but other sizes are affected
> +	 * according to forum posts */
> +	{ "PNY 1TB SATA SSD",		"H220916a",	ATA_QUIRK_NOLPM |
> +							ATA_QUIRK_1_5_GBPS |
> +							ATA_QUIRK_NONCQ },

Does this drive really need 1.5 Gbps quirk?
Right now we only have 2 drives with the ATA_QUIRK_1_5_GBPS quirk.

Ideally, it would be nice if we could just have a single quirk.
If for some reason a single quirk is not sufficient, then two quirks
is fine... But three quirks?

I'm not saying that it is impossible, but it is very rare that we have
seen a drive that requires three different quirks.


Kind regards,
Niklas

      reply	other threads:[~2026-11-07 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <[PATCH] ata: libata-core: Add quirks for PNY 1TB SATA SSD 916a>
2026-10-28 12:42 ` [PATCH] ata: libata-core: Add NOLPM quirk for PNY 1TB SATA SSD Thierry Vignaud
2026-10-28 12:54   ` sashiko-bot
2026-10-28 13:25     ` Thierry Vignaud
2026-10-28 14:54 ` [PATCH] ata: libata-core: Add NOLPM/NONCQ/1.5Gbps " Thierry Vignaud
2026-11-07 14:06   ` Niklas Cassel [this message]
     [not found] <[PATCH]>
     [not found] ` <ata:>
     [not found]   ` <libata-core:>
     [not found]     ` <Add>
     [not found]       ` <quirks>
     [not found]         ` <for>
     [not found]           ` <PNY>
     [not found]             ` <1TB>
     [not found]               ` <SATA>
     [not found]                 ` <SSD>

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=au8wfDKEh9Nzt3D0@ryzen \
    --to=cassel@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=tvignaud@redhat.com \
    /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