From: Xander Li <xander_li@kingston.corp-partner.google.com>
To: paulburton@kernel.org, kbusch@kernel.org, axboe@fb.com,
hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: ralf@linux-mips.org, jhogan@kernel.org, christian@brauner.io,
jeff_yang@kingston.corp-partner.google.com,
dora_chueh@kingston.corp-partner.google.com,
james_liu@kingston.corp-partner.google.com,
vincent_wu@kingston.com.tw, xander_li@kingston.com.tw,
Xander Li <xander_li@kingston.corp-partner.google.com>
Subject: [PATCH] nvme-pci-disable-write-zeros-support-on-kingston-SSD
Date: Fri, 30 Sep 2022 02:14:01 -0700 [thread overview]
Message-ID: <20220930091401.14862-1-xander_li@kingston.corp-partner.google.com> (raw)
---
drivers/nvme/host/pci.c | 10 ++++++++++
1 file changed, 10 insertions(+)
mode change 100644 => 100755 drivers/nvme/host/pci.c
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
old mode 100644
new mode 100755
index 98864b853eef..d08c8c854f3a
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -3503,6 +3503,16 @@ static const struct pci_device_id nvme_id_table[] = {
.driver_data = NVME_QUIRK_NO_DEEPEST_PS, },
{ PCI_DEVICE(0x2646, 0x2263), /* KINGSTON A2000 NVMe SSD */
.driver_data = NVME_QUIRK_NO_DEEPEST_PS, },
+ { PCI_DEVICE(0x2646, 0x5018), /* KINGSTON OM8SFP4xxxxP OS21012 NVMe SSD */
+ .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
+ { PCI_DEVICE(0x2646, 0x5016), /* KINGSTON OM3PGP4xxxxP OS21011 NVMe SSD */
+ .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
+ { PCI_DEVICE(0x2646, 0x501A), /* KINGSTON OM8PGP4xxxxP OS21005 NVMe SSD */
+ .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
+ { PCI_DEVICE(0x2646, 0x501B), /* KINGSTON OM8PGP4xxxxQ OS21005 NVMe SSD */
+ .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
+ { PCI_DEVICE(0x2646, 0x501E), /* KINGSTON OM3PGP4xxxxQ OS21011 NVMe SSD */
+ .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
{ PCI_DEVICE(0x1e4B, 0x1001), /* MAXIO MAP1001 */
.driver_data = NVME_QUIRK_BOGUS_NID, },
{ PCI_DEVICE(0x1e4B, 0x1002), /* MAXIO MAP1002 */
--
2.25.1
next reply other threads:[~2022-09-30 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 9:14 Xander Li [this message]
2022-10-03 7:18 ` Christoph Hellwig
2022-10-03 16:19 ` Bart Van Assche
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=20220930091401.14862-1-xander_li@kingston.corp-partner.google.com \
--to=xander_li@kingston.corp-partner.google.com \
--cc=axboe@fb.com \
--cc=christian@brauner.io \
--cc=dora_chueh@kingston.corp-partner.google.com \
--cc=hch@lst.de \
--cc=james_liu@kingston.corp-partner.google.com \
--cc=jeff_yang@kingston.corp-partner.google.com \
--cc=jhogan@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=paulburton@kernel.org \
--cc=ralf@linux-mips.org \
--cc=sagi@grimberg.me \
--cc=vincent_wu@kingston.com.tw \
--cc=xander_li@kingston.com.tw \
/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
all inboxes | Powered by JetHome®