From: Yazen Ghannam <yazen.ghannam@amd.com>
To: <linux-edac@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <bp@alien8.de>,
<mchehab@kernel.org>, <tony.luck@intel.com>,
<james.morse@arm.com>, <rric@kernel.org>,
<Smita.KoralahalliChannabasappa@amd.com>,
<william.roche@oracle.com>,
"Yazen Ghannam" <yazen.ghannam@amd.com>
Subject: [PATCH v3 0/2] AMD Family 19h Models 10h-1Fh Updates
Date: Tue, 28 Dec 2021 20:06:13 +0000 [thread overview]
Message-ID: <20211228200615.412999-1-yazen.ghannam@amd.com> (raw)
Hi all,
This set adds support for AMD Family 19h Models 10h-1Fh and A0h-AFh.
This set is based on the following branches:
- tip/master
- ras/edac-for-next
- groeck/linux-staging/hwmon-next
The following commit in hwmon-next is needed for functional support of
this set.
49e90c39d0be ("x86/amd_nb: Add AMD Family 19h Models (10h-1Fh) and (A0h-AFh) PCI IDs")
Patch 1 has been completely reworked into a new patch to support setting
the "memory type" per DIMM rather than assuming all DIMMs are the same.
Patch 2 adds register offset and other minor changes introduced with
these new models.
Thanks,
Yazen
Link:
https://lkml.kernel.org/r/20211215155309.2711917-1-yazen.ghannam@amd.com
v2->v3:
* Patch 1 completely reworked.
* Patch 2 updated based on comments from William.
Yazen Ghannam (2):
EDAC/amd64: Set memory type per DIMM
EDAC/amd64: Add new register offset support and related changes
drivers/edac/amd64_edac.c | 101 ++++++++++++++++++++++++++++++--------
drivers/edac/amd64_edac.h | 14 ++++++
2 files changed, 95 insertions(+), 20 deletions(-)
--
2.25.1
next reply other threads:[~2021-12-28 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 20:06 Yazen Ghannam [this message]
2021-12-28 20:06 ` [PATCH v3 1/2] EDAC/amd64: Set memory type per DIMM Yazen Ghannam
2021-12-28 20:06 ` [PATCH v3 2/2] EDAC/amd64: Add new register offset support and related changes Yazen Ghannam
2022-01-01 12:36 ` kernel test robot
2022-01-01 12:36 ` kernel test robot
2022-01-21 12:25 ` Borislav Petkov
2022-01-31 22:43 ` Yazen Ghannam
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=20211228200615.412999-1-yazen.ghannam@amd.com \
--to=yazen.ghannam@amd.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rric@kernel.org \
--cc=tony.luck@intel.com \
--cc=william.roche@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.