From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Avadhut Naik <avadhut.naik@amd.com>
Cc: linux-edac@vger.kernel.org, bp@alien8.de,
linux-kernel@vger.kernel.org, avadnaik@amd.com
Subject: Re: [PATCH] EDAC/amd64: Add support for AMD family 1Ah-based newer models
Date: Thu, 24 Jul 2025 09:24:30 -0400 [thread overview]
Message-ID: <20250724132430.GA985@yaz-khff2.amd.com> (raw)
In-Reply-To: <20250722192855.3108575-1-avadhut.naik@amd.com>
On Tue, Jul 22, 2025 at 07:27:31PM +0000, Avadhut Naik wrote:
> Add support for family 1Ah-based models 50h-57h, 90h-9Fh, A0h-AFh, and
> C0h-C7h.
>
> Signed-off-by: Avadhut Naik <avadhut.naik@amd.com>
> ---
> drivers/edac/amd64_edac.c | 20 ++++++++++++++++++++
> drivers/edac/amd64_edac.h | 2 +-
> 2 files changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c
> index 07f1e9dc1ca7..06ae6750ca14 100644
> --- a/drivers/edac/amd64_edac.c
> +++ b/drivers/edac/amd64_edac.c
> @@ -3923,6 +3923,26 @@ static int per_family_init(struct amd64_pvt *pvt)
> pvt->ctl_name = "F1Ah_M40h";
> pvt->flags.zn_regs_v2 = 1;
> break;
> + case 0x50 ... 0x57:
> + pvt->ctl_name = "F1Ah_M50h";
> + pvt->max_mcs = 16;
> + pvt->flags.zn_regs_v2 = 1;
> + break;
> + case 0x90 ... 0x9f:
> + pvt->ctl_name = "F1Ah_M90h";
> + pvt->max_mcs = 8;
> + pvt->flags.zn_regs_v2 = 1;
> + break;
> + case 0xa0 ... 0xaf:
> + pvt->ctl_name = "F1Ah_MA0h";
> + pvt->max_mcs = 8;
> + pvt->flags.zn_regs_v2 = 1;
> + break;
> + case 0xc0 ... 0xc7:
> + pvt->ctl_name = "F1Ah_MC0h";
> + pvt->max_mcs = 16;
These last three groups have extra tabs. Please align them with the
other lines.
> + pvt->flags.zn_regs_v2 = 1;
> + break;
> }
> break;
>
> diff --git a/drivers/edac/amd64_edac.h b/drivers/edac/amd64_edac.h
> index 17228d07de4c..d70b8a8d0b09 100644
> --- a/drivers/edac/amd64_edac.h
> +++ b/drivers/edac/amd64_edac.h
> @@ -96,7 +96,7 @@
> /* Hardware limit on ChipSelect rows per MC and processors per system */
> #define NUM_CHIPSELECTS 8
> #define DRAM_RANGES 8
> -#define NUM_CONTROLLERS 12
> +#define NUM_CONTROLLERS 16
The "legacy sysfs interface" needs an update too. I don't know if folks
still actively use it, but it hasn't been totally removed yet.
See this commit as an example:
25836ce1df82 ("EDAC/mc_sysfs: Increase legacy channel support to 12")
Thanks,
Yazen
next prev parent reply other threads:[~2025-07-24 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 19:27 Avadhut Naik
2025-07-24 13:24 ` Yazen Ghannam [this message]
2025-07-24 18:42 ` Naik, Avadhut
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=20250724132430.GA985@yaz-khff2.amd.com \
--to=yazen.ghannam@amd.com \
--cc=avadhut.naik@amd.com \
--cc=avadnaik@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.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®