From: Shashank Balaji <shashank.mahadasyam@sony.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-pm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
Shinya Takumi <shinya.takumi@sony.com>,
20250522-userspace-governor-doc-v1-1-c8a038e39084@sony.com
Subject: Re: [PATCH v2 0/2] cpufreq: userspace: add CPUFREQ_GOV_STRICT_TARGET flag
Date: Tue, 17 Jun 2025 19:14:58 +0900 [thread overview]
Message-ID: <aFFAIrGNlsGyKVLc@JPC00244420> (raw)
In-Reply-To: <20250527-userspace-governor-doc-v2-0-0e22c69920f2@sony.com>
Hi Rafael,
Could you please take a look at this?
Thanks
Regards,
Shashank
On Tue, May 27, 2025 at 09:59:08PM +0900, Shashank Balaji wrote:
> In-Reply-To: 20250522-userspace-governor-doc-v1-1-c8a038e39084@sony.com
> Signed-off-by: Shashank Balaji <shashank.mahadasyam@sony.com>
> ---
> Changes in v2:
> - Instead of modifying the documentation to say that variation in frequency is
> possible despite setting scaling_setspeed, add the CPUFREQ_GOV_STRICT_TARGET
> flag to the userspace governor to make its behaviour match the expectation when
> used with the intel_pstate driver with HWP enabled
> - Mention in the documentation that variation in frequency due to hardware
> factors is possible
> - Link to v1: https://lore.kernel.org/r/20250522-userspace-governor-doc-v1-1-c8a038e39084@sony.com
>
> ---
> Shashank Balaji (2):
> cpufreq: userspace: set CPUFREQ_GOV_STRICT_TARGET flag
> cpufreq, docs: userspace: mention variation in freq due to hw coordination
>
> Documentation/admin-guide/pm/cpufreq.rst | 4 +++-
> drivers/cpufreq/cpufreq_userspace.c | 1 +
> 2 files changed, 4 insertions(+), 1 deletion(-)
> ---
> base-commit: 914873bc7df913db988284876c16257e6ab772c6
> change-id: 20250522-userspace-governor-doc-86380dbab3d5
>
> Best regards,
> --
> Shashank Balaji <shashank.mahadasyam@sony.com>
>
next prev parent reply other threads:[~2025-06-17 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 12:59 [PATCH v2 0/2] cpufreq: userspace: add CPUFREQ_GOV_STRICT_TARGET flag Shashank Balaji
2025-05-27 12:59 ` [PATCH v2 1/2] cpufreq: userspace: set " Shashank Balaji
2025-05-27 12:59 ` [PATCH v2 2/2] cpufreq, docs: userspace: mention variation in freq due to hw coordination Shashank Balaji
2025-06-17 10:14 ` Shashank Balaji [this message]
2025-06-18 19:35 ` [PATCH v2 0/2] cpufreq: userspace: add CPUFREQ_GOV_STRICT_TARGET flag 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=aFFAIrGNlsGyKVLc@JPC00244420 \
--to=shashank.mahadasyam@sony.com \
--cc=20250522-userspace-governor-doc-v1-1-c8a038e39084@sony.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=shinya.takumi@sony.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.