Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Nader <dev@kayoway.com>
To: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me
Cc: linux-nvme@lists.infradead.org, Jason Nader <dev@kayoway.com>
Subject: [PATCH 1/1] nvme-pci: add quirks for Lexar NM790
Date: Thu, 23 May 2024 00:56:14 +0900	[thread overview]
Message-ID: <20240522155614.191849-2-dev@kayoway.com> (raw)
In-Reply-To: <20240522155614.191849-1-dev@kayoway.com>

NVME device 'Lexar SSD NM790 2TB', which shows in `lspci -nn` as
Shenzhen Longsys Electronics Co., Ltd. Lexar NM790 NVME SSD (DRAM-less) [1d97:1602] (rev 01),
shows the following warnings in dmesg:

nvme nvme1: missing or invalid SUBNQN field.
block nvme1n1: No UUID available providing old NGUID

To fix this, add IGNORE_DEV_SUBNQN and BOGUS_NID quirks for this device.

Signed-off-by: Jason Nader <dev@kayoway.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 710043086dff..8ca831cb2f79 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -3490,6 +3490,9 @@ static const struct pci_device_id nvme_id_table[] = {
 	{ PCI_DEVICE(0x1d97, 0x2269), /* Lexar NM760 */
 		.driver_data = NVME_QUIRK_BOGUS_NID |
 				NVME_QUIRK_IGNORE_DEV_SUBNQN, },
+	{ PCI_DEVICE(0x1d97, 0x1602), /* Lexar NM790 */
+		.driver_data = NVME_QUIRK_BOGUS_NID |
+				NVME_QUIRK_IGNORE_DEV_SUBNQN, },
 	{ PCI_DEVICE(0x10ec, 0x5763), /* TEAMGROUP T-FORCE CARDEA ZERO Z330 SSD */
 		.driver_data = NVME_QUIRK_BOGUS_NID, },
 	{ PCI_DEVICE(0x1e4b, 0x1602), /* HS-SSD-FUTURE 2048G  */
-- 
2.45.1



  reply	other threads:[~2024-05-22 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 15:56 [PATCH 0/1] nvme-pci: add quirks for Lexar NM790 Jason Nader
2024-05-22 15:56 ` Jason Nader [this message]
2024-05-22 17:42 ` Keith Busch
2024-05-23  9:52   ` Jason Nader

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=20240522155614.191849-2-dev@kayoway.com \
    --to=dev@kayoway.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@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