From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: hdegoede@redhat.com, markgross@kernel.org,
andriy.shevchenko@linux.intel.com,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: ISST: Allow reading core-power state on HWP disabled systems
Date: Mon, 04 Mar 2024 15:17:18 +0200 [thread overview]
Message-ID: <170955823884.5357.9018605202965437681.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20240229002659.1416623-1-srinivas.pandruvada@linux.intel.com>
On Wed, 28 Feb 2024 16:26:59 -0800, Srinivas Pandruvada wrote:
> When HWP (Hardware P-states) is disabled, dynamic SST features are
> disabled. But user should still be able to read the current core-power
> state, with legacy P-states. This will allow users to read current
> configuration with static SST enabled from BIOS.
>
> To address this, do not call disable_dynamic_sst_features() when the
> request is for reading the state.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo branch. Note it will show up in the public
platform-drivers-x86/review-ilpo branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/1] platform/x86: ISST: Allow reading core-power state on HWP disabled systems
commit: 959e640cf7b2d456052b346fa50574242ca56aaa
--
i.
prev parent reply other threads:[~2024-03-04 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 0:26 [PATCH] platform/x86: ISST: Allow reading core-power state on HWP disabled systems Srinivas Pandruvada
2024-02-29 12:32 ` Ilpo Järvinen
2024-02-29 15:11 ` srinivas pandruvada
2024-02-29 21:18 ` Kuppuswamy Sathyanarayanan
2024-03-04 13:17 ` Ilpo Järvinen [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=170955823884.5357.9018605202965437681.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.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