From: Holger Huo <holgerhuo@outlook.com>
To: kbusch@kernel.org, hch@lst.de, sagi@grimberg.me, axboe@kernel.dk
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Holger Huo <holgerhuo@outlook.com>, Holger Huo <i@holger.one>
Subject: [PATCH] drivers/nvme: Add quirks for device 1cc4:6a14
Date: Wed, 10 Apr 2024 03:28:50 +0800 [thread overview]
Message-ID: <ME3P282MB24818FA28E7C73BC01302882B5072@ME3P282MB2481.AUSP282.PROD.OUTLOOK.COM> (raw)
This commit adds NVME_QUIRK_BOGUS_NID for device [1cc4:6a14], the
Shenzhen Unionmemory Information System Ltd. RPEYJ1T24MKN2QWY PCIe
4.0 NVMe SSD 1024GB (DRAM-less), which can be found on many Lenovo
notebooks. This SSD produces all-zero nguid.
Other SSDs manufatured by Shenzhen Unionmemory Information System
Ltd are likely to face similar issues, but I currently have no
device to test.
Signed-off-by: Holger Huo <i@holger.one>
---
drivers/nvme/host/pci.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 8e0bb9692..b478b1736 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -3482,6 +3482,8 @@ static const struct pci_device_id nvme_id_table[] = {
.driver_data = NVME_QUIRK_BOGUS_NID, },
{ PCI_DEVICE(0x10ec, 0x5765), /* TEAMGROUP MP33 2TB SSD */
.driver_data = NVME_QUIRK_BOGUS_NID, },
+ { PCI_DEVICE(0x1cc4, 0x6a14), /* UMIS PCIe 4.0 NVMe SSD 1024GB (DRAM-less) */
+ .driver_data = NVME_QUIRK_BOGUS_NID, },
{ PCI_DEVICE(PCI_VENDOR_ID_AMAZON, 0x0061),
.driver_data = NVME_QUIRK_DMA_ADDRESS_BITS_48, },
{ PCI_DEVICE(PCI_VENDOR_ID_AMAZON, 0x0065),
--
2.44.0
next reply other threads:[~2024-04-09 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 19:28 Holger Huo [this message]
2024-04-09 20:14 ` [PATCH] drivers/nvme: Add quirks for device 1cc4:6a14 Keith Busch
2024-04-10 2:05 ` Holger Huo
2024-04-10 3:08 ` Keith Busch
2024-04-10 5:31 ` Holger Huo
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=ME3P282MB24818FA28E7C73BC01302882B5072@ME3P282MB2481.AUSP282.PROD.OUTLOOK.COM \
--to=holgerhuo@outlook.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=i@holger.one \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).