From: Artem Bityutskiy <dedekind1@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Mark Gross <markgross@kernel.org>,
platform-driver-x86@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Linux PM Mailing List <linux-pm@vger.kernel.org>
Subject: [PATCH resend] platform/x86: intel-uncore-freq: add Emerald Rapids support
Date: Tue, 22 Nov 2022 09:00:14 +0200 [thread overview]
Message-ID: <20221122070014.3639277-1-dedekind1@gmail.com> (raw)
From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Make Intel uncore frequency driver support Emerald Rapids by adding its CPU
model to the match table. Emerald Rapids uncore frequency control is the same
as in Sapphire Rapids.
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
---
Re-sending the same patch, but added X86 platform maintainers.
drivers/platform/x86/intel/uncore-frequency/uncore-frequency.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/platform/x86/intel/uncore-frequency/uncore-frequency.c b/drivers/platform/x86/intel/uncore-frequency/uncore-frequency.c
index 8f9c571d7257..00ac7e381441 100644
--- a/drivers/platform/x86/intel/uncore-frequency/uncore-frequency.c
+++ b/drivers/platform/x86/intel/uncore-frequency/uncore-frequency.c
@@ -203,6 +203,7 @@ static const struct x86_cpu_id intel_uncore_cpu_ids[] = {
X86_MATCH_INTEL_FAM6_MODEL(ICELAKE_X, NULL),
X86_MATCH_INTEL_FAM6_MODEL(ICELAKE_D, NULL),
X86_MATCH_INTEL_FAM6_MODEL(SAPPHIRERAPIDS_X, NULL),
+ X86_MATCH_INTEL_FAM6_MODEL(EMERALDRAPIDS_X, NULL),
{}
};
MODULE_DEVICE_TABLE(x86cpu, intel_uncore_cpu_ids);
--
2.37.3
next reply other threads:[~2022-11-22 7:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 7:00 Artem Bityutskiy [this message]
2022-11-22 15:30 ` [PATCH resend] platform/x86: intel-uncore-freq: add Emerald Rapids support Hans de Goede
2022-11-23 8:45 ` Artem Bityutskiy
2022-11-23 14:37 ` Hans de Goede
2022-11-23 14:59 ` Rafael J. Wysocki
2022-11-23 15:22 ` Rafael J. Wysocki
2022-11-23 15:54 ` Hans de Goede
2022-11-23 15:57 ` Rafael J. Wysocki
2022-11-23 17:25 ` srinivas pandruvada
2022-11-23 20:59 ` Hans de Goede
2022-11-24 7:04 ` Artem Bityutskiy
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=20221122070014.3639277-1-dedekind1@gmail.com \
--to=dedekind1@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-pm@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.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).