Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shminderjit Singh <shminderjit.singh@oracle.com>
To: kbusch@kernel.org, axboe@fb.com, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org
Cc: shminderjit.singh@oracle.com, junxiao.bi@oracle.com
Subject: [PATCH 1/1] nvme-pci: Add quirk for Samsung PM173X with Subsystem Vendor id:0x108e
Date: Fri, 16 May 2025 06:30:59 +0000	[thread overview]
Message-ID: <20250516063059.3456399-2-shminderjit.singh@oracle.com> (raw)
In-Reply-To: <20250516063059.3456399-1-shminderjit.singh@oracle.com>

This commit adds NVME_QUIRK_BOGUS_NSID for devices with Vendor ID 0x144d,
Device ID 0xa824 and Subsystem Vendor id 0x108e.

Signed-off-by: Shminderjit Singh <shminderjit.singh@oracle.com>
---
 drivers/nvme/host/pci.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 2e30e9be7408..767cdac056df 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -3163,6 +3163,13 @@ static unsigned long check_vendor_combination_bug(struct pci_dev *pdev)
 		    dmi_match(DMI_BOARD_NAME, "PH4PRX1_PH6PRX1") ||
 		    dmi_match(DMI_BOARD_NAME, "PH6PG01_PH6PG71"))
 			return NVME_QUIRK_FORCE_NO_SIMPLE_SUSPEND;
+	} else if (pdev->vendor == 0x144d && pdev->device == 0xa824 &&
+			pdev->subsystem_vendor == 0x108e) {
+		/*
+		 * Set NVME_QUIRK_BOGUS_NID for Samsung PM173X
+		 * with subsystem vendor id 0x108e.
+		 */
+		return NVME_QUIRK_BOGUS_NID;
 	}
 
 	/*
-- 
2.43.5



  reply	other threads:[~2025-05-16  6:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16  6:30 [PATCH 0/1] Add quirk for Samsung PM173X with Subsystem Vendor Shminderjit Singh
2025-05-16  6:30 ` Shminderjit Singh [this message]
2025-05-16  6:36   ` [PATCH 1/1] nvme-pci: Add quirk for Samsung PM173X with Subsystem Vendor id:0x108e Christoph Hellwig
2025-05-16  7:13     ` Shminderjit Singh
2025-05-16  7:15       ` Christoph Hellwig
2025-05-16  8:13         ` [External] : " Shminderjit Singh

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=20250516063059.3456399-2-shminderjit.singh@oracle.com \
    --to=shminderjit.singh@oracle.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=junxiao.bi@oracle.com \
    --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