From: wuxy@bitland.com.cn
To: kbusch@kernel.org, axboe@fb.com, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
evgreen@chromium.org, rajatja@google.com
Cc: wuxy <wuxy@bitland.corp-partner.google.com>, wuxy@bitland.com.cn
Subject: [PATCH] nvme: Add quirk for "SAMSUNG MZALQ128HBHQ-000L2"
Date: Tue, 17 Dec 2019 16:34:30 +0800 [thread overview]
Message-ID: <20191217083430.3269-1-wuxy@bitland.com.cn> (raw)
From: wuxy <wuxy@bitland.corp-partner.google.com>
Samsung SSD with model number:SAMSUNG MZALQ128HBHQ-000L2 has no response
when doing the "suspend/resume" test.This patch applied
NVME_QUIRK_SIMPLE_SUSPEND to fix this issue.Run the 2500 cycles
"suspend/resume" test after applying this patch and the issue can not
be reproduced again.Co-work with Samsung,they will fix this issue
in future firmware.
BUG= https://partnerissuetracker.corp.google.com/issues/144257635
TEST= run 2500 cycles "suspend/resume" test,the result is passed.
Signed-off-by: Xingyu Wu <wuxy@bitland.corp-partner.google.com>
---
drivers/nvme/host/core.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 667f18f465be..d16d12abec50 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -2414,6 +2414,16 @@ static const struct nvme_core_quirk_entry core_quirks[] = {
.vid = 0x14a4,
.fr = "22301111",
.quirks = NVME_QUIRK_SIMPLE_SUSPEND,
+ },
+ {
+ /*
+ * This Samsung SSD encountered no repsonse issue when
+ * running suspend to idle test.
+ * Samsung will fix this issue in future firmware.
+ */
+ .vid = 0x144d,
+ .mn = "SAMSUNG MZALQ128HBHQ-000L2",
+ .quirks = NVME_QUIRK_SIMPLE_SUSPEND,
}
};
--
2.17.1
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
reply other threads:[~2019-12-17 8:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191217083430.3269-1-wuxy@bitland.com.cn \
--to=wuxy@bitland.com.cn \
--cc=axboe@fb.com \
--cc=evgreen@chromium.org \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=rajatja@google.com \
--cc=sagi@grimberg.me \
--cc=wuxy@bitland.corp-partner.google.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;
as well as URLs for NNTP newsgroup(s).