linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: rafael@kernel.org, viresh.kumar@linaro.org,
	linux-pm@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: intel_pstate: Support Clearwater Forest OOB mode
Date: Mon, 11 Aug 2025 21:53:41 +0200	[thread overview]
Message-ID: <CAJZ5v0hOQdi-73fCDTfrRoKU_umaUNReH-8sTW8Q_uK_V5Ap3Q@mail.gmail.com> (raw)
In-Reply-To: <20250808145122.4057208-1-srinivas.pandruvada@linux.intel.com>

On Fri, Aug 8, 2025 at 4:51 PM Srinivas Pandruvada
<srinivas.pandruvada@linux.intel.com> wrote:
>
> Prevent intel_pstate from loading when OOB (Out Of Band) P-states mode is
> enabled.
>
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
>  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 06a1c7dd081f..f366d35c5840 100644
> --- a/drivers/cpufreq/intel_pstate.c
> +++ b/drivers/cpufreq/intel_pstate.c
> @@ -2793,6 +2793,7 @@ static const struct x86_cpu_id intel_pstate_cpu_oob_ids[] __initconst = {
>         X86_MATCH(INTEL_GRANITERAPIDS_X,        core_funcs),
>         X86_MATCH(INTEL_ATOM_CRESTMONT,         core_funcs),
>         X86_MATCH(INTEL_ATOM_CRESTMONT_X,       core_funcs),
> +       X86_MATCH(INTEL_ATOM_DARKMONT_X,        core_funcs),
>         {}
>  };
>  #endif
> --

Applied as 6.17-rc material, thanks!

      reply	other threads:[~2025-08-11 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08 14:51 [PATCH] cpufreq: intel_pstate: Support Clearwater Forest OOB mode Srinivas Pandruvada
2025-08-11 19:53 ` Rafael J. Wysocki [this message]

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=CAJZ5v0hOQdi-73fCDTfrRoKU_umaUNReH-8sTW8Q_uK_V5Ap3Q@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --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).