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>,
Christoph Hellwig <hch@lst.de>,
Jon Derrick <jonathan.derrick@intel.com>
Subject: [PATCH 1/5] PCI: Add Intel VMD devices to pci ids
Date: Fri, 18 May 2018 13:27:58 -0600 [thread overview]
Message-ID: <20180518192802.20371-2-jonathan.derrick@intel.com> (raw)
In-Reply-To: <20180518192802.20371-1-jonathan.derrick@intel.com>
Add the Intel VMD device ids to the pci id database and update the VMD
driver.
Signed-off-by: Jon Derrick <jonathan.derrick@intel.com>
---
drivers/pci/host/vmd.c | 2 +-
include/linux/pci_ids.h | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/pci/host/vmd.c b/drivers/pci/host/vmd.c
index 930a8fa08bd6..b10d2bce2993 100644
--- a/drivers/pci/host/vmd.c
+++ b/drivers/pci/host/vmd.c
@@ -778,7 +778,7 @@ static int vmd_resume(struct device *dev)
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, PCI_DEVICE_ID_INTEL_VMD_201D),},
{0,}
};
MODULE_DEVICE_TABLE(pci, vmd_ids);
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index 9cd0a41e72dd..206d6b9ef434 100644
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@ -2676,6 +2676,7 @@
#define PCI_DEVICE_ID_INTEL_PANTHERPOINT_XHCI 0x1e31
#define PCI_DEVICE_ID_INTEL_PANTHERPOINT_LPC_MIN 0x1e40
#define PCI_DEVICE_ID_INTEL_PANTHERPOINT_LPC_MAX 0x1e5f
+#define PCI_DEVICE_ID_INTEL_VMD_201D 0x201d
#define PCI_DEVICE_ID_INTEL_DH89XXCC_LPC_MIN 0x2310
#define PCI_DEVICE_ID_INTEL_DH89XXCC_LPC_MAX 0x231f
#define PCI_DEVICE_ID_INTEL_82801AA_0 0x2410
@@ -2780,6 +2781,7 @@
#define PCI_DEVICE_ID_INTEL_ICH8_4 0x2815
#define PCI_DEVICE_ID_INTEL_ICH8_5 0x283e
#define PCI_DEVICE_ID_INTEL_ICH8_6 0x2850
+#define PCI_DEVICE_ID_INTEL_VMD_28C0 0x28c0
#define PCI_DEVICE_ID_INTEL_ICH9_0 0x2910
#define PCI_DEVICE_ID_INTEL_ICH9_1 0x2917
#define PCI_DEVICE_ID_INTEL_ICH9_2 0x2912
--
2.14.3
next prev parent reply other threads:[~2018-05-18 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 19:27 [PATCH 0/5] Enable an additional VMD device id Jon Derrick
2018-05-18 19:27 ` Jon Derrick [this message]
2018-05-18 19:27 ` [PATCH 2/5] PCI/VMD: Assign membar addresses from shadow registers Jon Derrick
2018-05-18 19:28 ` [PATCH 3/5] PCI/VMD: Add offset to bus numbers if necessary Jon Derrick
2018-05-18 19:28 ` [PATCH 4/5] x86/PCI: Add additional VMD device root ports to VMD AER quirk Jon Derrick
2018-05-24 13:37 ` Bjorn Helgaas
2018-05-18 19:28 ` [PATCH 5/5] PCI/VMD: Add an additional VMD device id to driver device id table Jon Derrick
2018-05-24 11:44 ` [PATCH 0/5] Enable an additional VMD device id Lorenzo Pieralisi
2018-05-24 16:15 ` Derrick, Jonathan
2018-05-24 16:34 ` Lorenzo Pieralisi
2018-05-24 16:36 ` Derrick, Jonathan
2018-05-24 16:58 ` Lorenzo Pieralisi
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=20180518192802.20371-2-jonathan.derrick@intel.com \
--to=jonathan.derrick@intel.com \
--cc=david.fugate@intel.com \
--cc=hch@lst.de \
--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).