public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/3] libata: Apply NOLPM quirk to Crucial M500 480 and 960GB SSDs
Date: Mon, 19 Mar 2018 08:37:22 -0700	[thread overview]
Message-ID: <20180319153722.GP2943022@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20180319153400.25694-1-hdegoede@redhat.com>

On Mon, Mar 19, 2018 at 04:33:58PM +0100, Hans de Goede wrote:
> There have been reports of the Crucial M500 480GB model not working
> with LPM set to min_power / med_power_with_dipm level.
> 
> It has not been tested with medium_power, but that typically has no
> measurable power-savings.
> 
> Note the reporters Crucial_CT480M500SSD3 has a firmware version of MU03
> and there is a MU05 update available, but that update does not mention any
> LPM fixes in its changelog, so the quirk matches all firmware versions.
> 
> In my experience the LPM problems with (older) Crucial SSDs seem to be
> limited to higher capacity versions of the SSDs (different firmware?),
> so this commit adds a NOLPM quirk for the 480 and 960GB versions of the
> M500, to avoid LPM causing issues with these SSDs.
> 
> Cc: stable@vger.kernel.org
> Reported-and-tested-by: Martin Steigerwald <martin@lichtvoll.de>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>

Applied 1-3 to libata/for-4.16-fixes.

Thanks.

-- 
tejun

      parent reply	other threads:[~2018-03-19 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 15:33 [PATCH 1/3] libata: Apply NOLPM quirk to Crucial M500 480 and 960GB SSDs Hans de Goede
2018-03-19 15:33 ` [PATCH 2/3] libata: Make Crucial BX100 500GB LPM quirk apply to all firmware versions Hans de Goede
2018-03-19 15:34 ` [PATCH 3/3] libata: Modify quirks for MX100 to limit NCQ_TRIM quirk to MU01 version Hans de Goede
2018-03-19 15:37 ` Tejun Heo [this message]

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=20180319153722.GP2943022@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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