From: "Derrick, Jonathan" <jonathan.derrick@intel.com>
To: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "N, Shyjumon" <shyjumon.n@intel.com>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"axboe@fb.com" <axboe@fb.com>,
"Nadolski, Edmund" <edmund.nadolski@intel.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH] nvme/pci: Add sleep quirk for Samsung and Toshiba drives
Date: Wed, 22 Jan 2020 17:25:26 +0000 [thread overview]
Message-ID: <d74ae02c0a560973fda9b35acc5e5f16e1438fac.camel@intel.com> (raw)
In-Reply-To: <20200121193012.29360-1-jonathan.derrick@intel.com>
On Tue, 2020-01-21 at 12:30 -0700, Jon Derrick wrote:
> From: shyjumon <shyjumon.n@intel.com>
>
> From: Shyjumon N <shyjumon.n@intel.com>
>
> The Samsung SSD SM981/PM981 and Toshiba SSD KBG40ZNT256G on the Lenovo
> C640 platform experience runtime resume issues when the SSDs are kept in
> sleep/suspend mode for long time.
>
> This patch applies the 'Simple Suspend' quirk to these configurations.
> With this patch, the issue had not been observed in a 1+ day test.
>
> Signed-off-by: Jon Derrick <jonathan.derrick@intel.com>
> [jonathan.derrick: fix up commit message]
> Signed-off-by: Shyjumon N <shyjumon.n@intel.com>
Sorry the signoff ordering is reversed here. Should be Shyjumon first.
That being said, I wonder if there's something else the driver should
be doing for the whole range of devices and platform combos that seem
to require similar pm quirks.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-01-22 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 19:30 [PATCH] nvme/pci: Add sleep quirk for Samsung and Toshiba drives Jon Derrick
2020-01-22 17:25 ` Derrick, Jonathan [this message]
2020-01-30 14:55 ` Christoph Hellwig
2020-02-03 16:19 ` Derrick, Jonathan
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=d74ae02c0a560973fda9b35acc5e5f16e1438fac.camel@intel.com \
--to=jonathan.derrick@intel.com \
--cc=axboe@fb.com \
--cc=edmund.nadolski@intel.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shyjumon.n@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