From: Jon Derrick <jonathan.derrick@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Keith Busch <keith.busch@intel.com>, <linux-pci@vger.kernel.org>
Cc: Joerg Roedel <jroedel@suse.de>,
Myron Stowe <myron.stowe@redhat.com>,
Dave Fugate <david.fugate@intel.com>,
Scott Bauer <scott.bauer@intel.com>,
Jon Derrick <jonathan.derrick@intel.com>
Subject: [RFC PATCH 4/4] PCI/VMD: Add new VMD device id to driver device id table
Date: Thu, 10 May 2018 18:49:03 -0600 [thread overview]
Message-ID: <20180511004903.19892-5-jonathan.derrick@intel.com> (raw)
In-Reply-To: <20180511004903.19892-1-jonathan.derrick@intel.com>
Allow new VMD hardware to bind to VMD driver.
Signed-off-by: Jon Derrick <jonathan.derrick@intel.com>
---
drivers/pci/host/vmd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pci/host/vmd.c b/drivers/pci/host/vmd.c
index fdfc286a1c9e..add940eedc56 100644
--- a/drivers/pci/host/vmd.c
+++ b/drivers/pci/host/vmd.c
@@ -831,6 +831,7 @@ static SIMPLE_DEV_PM_OPS(vmd_dev_pm_ops, vmd_suspend, vmd_resume);
static const struct pci_device_id vmd_ids[] = {
{PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x201d),},
+ {PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x28c0),},
{0,}
};
MODULE_DEVICE_TABLE(pci, vmd_ids);
--
2.14.3
prev parent reply other threads:[~2018-05-11 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 0:48 [RFC PATCH 0/4] Enable new VMD device Jon Derrick
2018-05-11 0:49 ` [RFC PATCH 1/4] PCI/VMD: Assign membar addresses from shadow registers Jon Derrick
2018-05-14 14:23 ` Christoph Hellwig
2018-05-11 0:49 ` [RFC PATCH 2/4] PCI/VMD: Add offset to bus numbers if necessary Jon Derrick
2018-05-11 0:49 ` [RFC PATCH 3/4] x86/PCI: Add new VMD device root ports to VMD AER quirk Jon Derrick
2018-05-11 0:49 ` Jon Derrick [this message]
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=20180511004903.19892-5-jonathan.derrick@intel.com \
--to=jonathan.derrick@intel.com \
--cc=david.fugate@intel.com \
--cc=helgaas@kernel.org \
--cc=jroedel@suse.de \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=myron.stowe@redhat.com \
--cc=scott.bauer@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;
as well as URLs for NNTP newsgroup(s).