From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: "Yuan, Perry" <Perry.Yuan@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Huang, Ray" <Ray.Huang@amd.com>,
"Limonciello, Mario" <mario.limonciello@amd.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Sasha Levin <sashal@kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [REGRESSION] amd-pstate doesn't work since v5.18.11
Date: Tue, 12 Jul 2022 23:55:05 +0200 [thread overview]
Message-ID: <6967031.z0QvQKZeIK@natalenko.name> (raw)
In-Reply-To: <4c9e3a4c-40b2-3ce9-da88-ad507769658b@amd.com>
Hello.
On úterý 12. července 2022 22:07:15 CEST Limonciello, Mario wrote:
> See if this helps out:
>
> diff --git a/arch/x86/kernel/acpi/cppc.c b/arch/x86/kernel/acpi/cppc.c
> index 734b96454896..88a81e6b9228 100644
> --- a/arch/x86/kernel/acpi/cppc.c
> +++ b/arch/x86/kernel/acpi/cppc.c
> @@ -16,6 +16,13 @@ bool cpc_supported_by_cpu(void)
> switch (boot_cpu_data.x86_vendor) {
> case X86_VENDOR_AMD:
> case X86_VENDOR_HYGON:
> + if (boot_cpu_data.x86 == 0x19 &&
> + ((boot_cpu_data.x86_model >= 0x00 &&
> boot_cpu_data.x86_model <= 0x0f) ||
> + (boot_cpu_data.x86_model >= 0x20 &&
> boot_cpu_data.x86_model <= 0x2f)))
> + return true;
> + else if (boot_cpu_data.x86 == 0x17 &&
> + boot_cpu_data.x86_model >= 0x70 &&
> boot_cpu_data.x86_model <= 0x7f)
> + return true;
> return boot_cpu_has(X86_FEATURE_CPPC);
> }
> return false;
>
> If that works and no one has a better idea how to do it for these
> systems I'll send out a proper proper patch tomorrow.
This patch (also mirrored here [1]) works for me, thanks.
[1] https://codeberg.org/pf-kernel/linux/commit/cc5c57b8c349c85b81b44cf5fe2d2577b947a7de
--
Oleksandr Natalenko (post-factum)
next prev parent reply other threads:[~2022-07-12 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 17:40 [REGRESSION] amd-pstate doesn't work since v5.18.11 Oleksandr Natalenko
2022-07-12 17:49 ` Yuan, Perry
2022-07-12 17:50 ` Limonciello, Mario
2022-07-12 17:54 ` Oleksandr Natalenko
2022-07-12 20:07 ` Limonciello, Mario
2022-07-12 21:55 ` Oleksandr Natalenko [this message]
2022-07-13 2:40 ` Yuan, Perry
2022-07-13 3:10 ` Mario Limonciello
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=6967031.z0QvQKZeIK@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=Perry.Yuan@amd.com \
--cc=Ray.Huang@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sashal@kernel.org \
--cc=x86@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