From: Giovanni Gherdovich <ggherdovich@suse.cz>
To: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Doug Smythies <dsmythies@telus.net>, Len Brown <lenb@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Giovanni Gherdovich <ggherdovich@suse.cz>
Subject: [PATCH v3 1/2] cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode
Date: Tue, 18 May 2021 14:34:12 +0200 [thread overview]
Message-ID: <20210518123413.20670-1-ggherdovich@suse.cz> (raw)
In-Reply-To: <CAJZ5v0g5_BY3DCi=VxqkRh+TYPS5nkJ-J96EzPVrc975uiWf3Q@mail.gmail.com>
Users may disable HWP in firmware, in which case intel_pstate wouldn't load
unless the CPU model is explicitly supported.
Add ICELAKE_X to the list of CPUs that can register intel_pstate while not
advertising the HWP capability. Without this change, an ICELAKE_X in no-HWP
mode could only use the acpi_cpufreq frequency scaling driver.
See also commit d8de7a44e11f ("cpufreq: intel_pstate: Add Skylake servers
support").
Signed-off-by: Giovanni Gherdovich <ggherdovich@suse.cz>
---
This replaces https://lore.kernel.org/lkml/20210513132051.31465-1-ggherdovich@suse.cz
drivers/cpufreq/intel_pstate.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
index 0e69dffd5a76..9a93603acd3f 100644
--- a/drivers/cpufreq/intel_pstate.c
+++ b/drivers/cpufreq/intel_pstate.c
@@ -2087,6 +2087,7 @@ static const struct x86_cpu_id intel_pstate_cpu_ids[] = {
X86_MATCH(ATOM_GOLDMONT, core_funcs),
X86_MATCH(ATOM_GOLDMONT_PLUS, core_funcs),
X86_MATCH(SKYLAKE_X, core_funcs),
+ X86_MATCH(ICELAKE_X, core_funcs),
{}
};
MODULE_DEVICE_TABLE(x86cpu, intel_pstate_cpu_ids);
--
2.26.2
next prev parent reply other threads:[~2021-05-18 12:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 7:59 [PATCH] cpufreq: intel_pstate: Force intel_pstate to load when HWP disabled in firmware Giovanni Gherdovich
2021-05-13 9:24 ` Srinivas Pandruvada
2021-05-13 10:10 ` Giovanni Gherdovich
2021-05-13 11:03 ` Srinivas Pandruvada
2021-05-13 12:10 ` Giovanni Gherdovich
2021-05-13 13:20 ` [PATCH v2] cpufreq: intel_pstate: Add Icelake servers support in no-HWP mode Giovanni Gherdovich
2021-05-14 15:31 ` Doug Smythies
2021-05-14 20:33 ` Giovanni Gherdovich
2021-05-14 22:12 ` Doug Smythies
2021-09-07 15:45 ` Doug Smythies
2021-09-07 16:01 ` Srinivas Pandruvada
2021-09-07 20:16 ` Doug Smythies
2021-09-08 2:04 ` Srinivas Pandruvada
2021-09-08 3:43 ` Doug Smythies
2021-09-14 18:41 ` Doug Smythies
2021-09-15 9:38 ` Srinivas Pandruvada
2021-05-15 2:58 ` Srinivas Pandruvada
2021-05-17 15:26 ` Rafael J. Wysocki
2021-05-18 11:33 ` Giovanni Gherdovich
2021-05-19 5:37 ` Doug Smythies
2021-05-18 12:34 ` Giovanni Gherdovich [this message]
2021-05-18 12:34 ` [PATCH v3 2/2] cpufreq: intel_pstate: Add Cometlake " Giovanni Gherdovich
2021-05-21 16:49 ` [PATCH v3 1/2] cpufreq: intel_pstate: Add Icelake servers " Rafael J. Wysocki
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=20210518123413.20670-1-ggherdovich@suse.cz \
--to=ggherdovich@suse.cz \
--cc=dsmythies@telus.net \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).