From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme: Quirks for PM1725 controllers
Date: Wed, 28 Jun 2017 12:44:50 -0400 [thread overview]
Message-ID: <20170628164449.GA2650@localhost.localdomain> (raw)
In-Reply-To: <f3690fd0-caa7-fb84-3a81-9a90c90f6db4@grimberg.me>
On Wed, Jun 28, 2017@10:27:09AM +0300, Sagi Grimberg wrote:
>
> > PM1725 controllers have a couple of quirks that need to be handled in
> > the driver:
> >
> > - I/O queue depth must be limited to 64 entries on controllers that do
> > not report MQES.
>
> I think this can be a new quirk (NVME_QUIRK_QD_LIMIT_64 or something)
>
> > @@ -1908,6 +1908,12 @@ static int nvme_pci_enable(struct nvme_dev *dev)
> > dev_warn(dev->ctrl.device, "detected Apple NVMe controller, "
> > "set queue depth=%u to work around controller resets\n",
> > dev->q_depth);
> > + } else if (pdev->vendor == PCI_VENDOR_ID_SAMSUNG &&
> > + (pdev->device == 0xa821 || pdev->device == 0xa822) &&
> > + NVME_CAP_MQES(cap) == 0) {
>
> and the this is:
>
> } else if (dev->ctrl.quirks & NVME_QUIRK_QD_LIMIT_64) {
>
> While its inside the pci driver, I think it would be cleaner to
> use the quirks mechanism.
>
> Kieth? thoughts?
Yeah, that's better than VID:DID checks. We only get 32 defined quirks
using driver_data, and while we currently can spare 2 of them for q-depth
quirks, I was hoping to use these bits more sparingly.
next prev parent reply other threads:[~2017-06-28 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 2:27 [PATCH] nvme: Quirks for PM1725 controllers Martin K. Petersen
2017-06-28 7:27 ` Sagi Grimberg
2017-06-28 16:44 ` Keith Busch [this message]
2017-06-28 16:51 ` Martin K. Petersen
2017-07-01 21:31 ` Martin K. Petersen
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=20170628164449.GA2650@localhost.localdomain \
--to=keith.busch@intel.com \
/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