From: Jiping Ma <jiping.ma2@windriver.com>
To: <jbaron@akamai.com>
Cc: <linux-edac@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<mchehab@kernel.org>, <bp@alien8.de>, <jiping.ma2@windriver.com>
Subject: [PATCH] EDAC, ie31200: Add Intel Corporation 3rd Gen Core processor
Date: Wed, 19 Jun 2019 15:15:18 +0800 [thread overview]
Message-ID: <1560928518-243100-2-git-send-email-jiping.ma2@windriver.com> (raw)
In-Reply-To: <1560928518-243100-1-git-send-email-jiping.ma2@windriver.com>
3rd Gen Core seems to work just like Skylake.
Signed-off-by: Jiping Ma <jiping.ma2@windriver.com>
---
drivers/edac/ie31200_edac.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/edac/ie31200_edac.c b/drivers/edac/ie31200_edac.c
index aac9b9b..1445336 100644
--- a/drivers/edac/ie31200_edac.c
+++ b/drivers/edac/ie31200_edac.c
@@ -19,6 +19,7 @@
* 0c08: Xeon E3-1200 v3 Processor DRAM Controller
* 1918: Xeon E3-1200 v5 Skylake Host Bridge/DRAM Registers
* 5918: Xeon E3-1200 Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers
+ * 0154: 3rd Gen Core processor DRAM Controller
*
* Based on Intel specification:
* http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/xeon-e3-1200v3-vol-2-datasheet.pdf
@@ -59,6 +60,7 @@
#define PCI_DEVICE_ID_INTEL_IE31200_HB_7 0x0c08
#define PCI_DEVICE_ID_INTEL_IE31200_HB_8 0x1918
#define PCI_DEVICE_ID_INTEL_IE31200_HB_9 0x5918
+#define PCI_DEVICE_ID_INTEL_IE31200_HB_10 0x0154
#define IE31200_DIMMS 4
#define IE31200_RANKS 8
@@ -569,6 +571,9 @@ static void ie31200_remove_one(struct pci_dev *pdev)
PCI_VEND_DEV(INTEL, IE31200_HB_9), PCI_ANY_ID, PCI_ANY_ID, 0, 0,
IE31200},
{
+ PCI_VEND_DEV(INTEL, IE31200_HB_10), PCI_ANY_ID, PCI_ANY_ID, 0, 0
+ , IE31200},
+ {
0,
} /* 0 terminated list. */
};
--
1.9.1
next prev parent reply other threads:[~2019-06-19 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 7:15 Review request for edac: " Jiping Ma
2019-06-19 7:15 ` Jiping Ma [this message]
2019-08-12 17:16 ` [PATCH] EDAC, " Tony Luck
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=1560928518-243100-2-git-send-email-jiping.ma2@windriver.com \
--to=jiping.ma2@windriver.com \
--cc=bp@alien8.de \
--cc=jbaron@akamai.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
/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®