From: Pascal Terjan <pterjan@google.com>
To: linux-nvme@lists.infradead.org
Cc: Pascal Terjan <pterjan@google.com>
Subject: [PATCH] nvme: Add quirks for Lexar 256GB SSD
Date: Tue, 23 Feb 2021 22:10:46 +0000 [thread overview]
Message-ID: <20210223221046.3367795-1-pterjan@google.com> (raw)
Add NVME_QUIRK_NO_NS_DESC_LIST to Lexar 256GB SSD to allow it to
work again, and add NVME_QUIRK_IGNORE_DEV_SUBNQN to avoid a warning.
[ 0.637476] nvme nvme0: missing or invalid SUBNQN field.
[ 0.638399] nvme nvme0: Identify Descriptors failed (16386)
Reported and tested in https://bugs.mageia.org/show_bug.cgi?id=28417
Signed-off-by: Pascal Terjan <pterjan@google.com>
---
drivers/nvme/host/pci.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 7b6632c00ffd..9a56ec70e93a 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -3232,6 +3232,9 @@ static const struct pci_device_id nvme_id_table[] = {
NVME_QUIRK_DISABLE_WRITE_ZEROES, },
{ PCI_DEVICE(0x126f, 0x2263), /* Silicon Motion unidentified */
.driver_data = NVME_QUIRK_NO_NS_DESC_LIST, },
+ { PCI_DEVICE(0x1b4b, 0x1092), /* Lexar 256 GB SSD */
+ .driver_data = NVME_QUIRK_NO_NS_DESC_LIST |
+ NVME_QUIRK_IGNORE_DEV_SUBNQN, },
{ PCI_DEVICE(0x1bb1, 0x0100), /* Seagate Nytro Flash Storage */
.driver_data = NVME_QUIRK_DELAY_BEFORE_CHK_RDY, },
{ PCI_DEVICE(0x1c58, 0x0003), /* HGST adapter */
--
2.30.0.617.g56c4b15f3c-goog
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-02-23 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 22:10 Pascal Terjan [this message]
2021-02-24 7:21 ` [PATCH] nvme: Add quirks for Lexar 256GB SSD Chaitanya Kulkarni
2021-02-24 9:21 ` Christoph Hellwig
2021-02-24 10:23 ` Pascal Terjan
2021-02-25 16:22 ` Keith Busch
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=20210223221046.3367795-1-pterjan@google.com \
--to=pterjan@google.com \
--cc=linux-nvme@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).