public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Niklas Cassel <cassel@kernel.org>,
	Mario Limonciello <mario.limonciello@amd.com>,
	Jian-Hong Pan <jhp@endlessos.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
	Basavaraj Natikar <Basavaraj.Natikar@amd.com>,
	Eric <eric.4.debian@grabatoulnz.fr>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: libata-core: Add ATA_QUIRK_NO_LPM_ON_ATI for certain Samsung SSDs
Date: Tue, 18 Mar 2025 17:41:43 +0900	[thread overview]
Message-ID: <9a19142f-4e93-46cd-9c23-3aaa0ebed5a5@kernel.org> (raw)
In-Reply-To: <20250317170348.1748671-2-cassel@kernel.org>

On 3/18/25 2:03 AM, Niklas Cassel wrote:
> Before commit 7627a0edef54 ("ata: ahci: Drop low power policy board type")
> the ATI AHCI controllers specified board type 'board_ahci' rather than
> board type 'board_ahci'. This means that LPM was historically not enabled
> for the ATI AHCI controllers.
> 
> By looking at commit 7a8526a5cd51 ("libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI
> for Samsung 860 and 870 SSD."), it is clear that, for some unknown reason,
> that Samsung SSDs do not play nice with ATI AHCI controllers. (When using
> other AHCI controllers, NCQ can be enabled on these Samsung SSDs without
> issues.)
> 
> In a similar way, from user reports, it is clear the ATI AHCI controllers
> can enable LPM on e.g. Maxtor HDDs perfectly fine, but when enabling LPM
> on certain Samsung SSDs, things break. (E.g. the SSDs will not get detected
> by the ATI AHCI controller even after a COMRESET.)
> 
> Yet, when using LPM on these Samsung SSDs with other AHCI controllers, e.g.
> Intel AHCI controllers, these Samsung drives appear to work perfectly fine.
> 
> Considering that the combination of ATI + Samsung, for some unknown reason,
> does not seem to work well, disable LPM when detecting an ATI AHCI
> controller with a problematic Samsung SSD.
> 
> Apply this new ATA_QUIRK_NO_LPM_ON_ATI quirk for all Samsung SSDs that have
> already been reported to not play nice with ATI (ATA_QUIRK_NO_NCQ_ON_ATI).
> 
> Fixes: 7627a0edef54 ("ata: ahci: Drop low power policy board type")
> Reported-by: Eric <eric.4.debian@grabatoulnz.fr>
> Closes: https://lore.kernel.org/linux-ide/Z8SBZMBjvVXA7OAK@eldamar.lan/
> Signed-off-by: Niklas Cassel <cassel@kernel.org>

Looks OK to me.

Reviewed-by: Damien Le Moal <dlemoal@kernel.org>

-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2025-03-18  8:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 17:03 [PATCH] ata: libata-core: Add ATA_QUIRK_NO_LPM_ON_ATI for certain Samsung SSDs Niklas Cassel
2025-03-18  8:41 ` Damien Le Moal [this message]
2025-03-18  9:14 ` Niklas Cassel

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=9a19142f-4e93-46cd-9c23-3aaa0ebed5a5@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=carnil@debian.org \
    --cc=cassel@kernel.org \
    --cc=eric.4.debian@grabatoulnz.fr \
    --cc=hdegoede@redhat.com \
    --cc=jhp@endlessos.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mika.westerberg@linux.intel.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