From: Shashank Balaji <shashank.mahadasyam@sony.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-pm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shinya Takumi <shinya.takumi@sony.com>,
20250522-userspace-governor-doc-v1-1-c8a038e39084@sony.com,
Shashank Balaji <shashank.mahadasyam@sony.com>
Subject: [PATCH v2 2/2] cpufreq, docs: userspace: mention variation in freq due to hw coordination
Date: Tue, 27 May 2025 21:59:10 +0900 [thread overview]
Message-ID: <20250527-userspace-governor-doc-v2-2-0e22c69920f2@sony.com> (raw)
In-Reply-To: <20250527-userspace-governor-doc-v2-0-0e22c69920f2@sony.com>
Signed-off-by: Shashank Balaji <shashank.mahadasyam@sony.com>
---
Documentation/admin-guide/pm/cpufreq.rst | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/pm/cpufreq.rst b/Documentation/admin-guide/pm/cpufreq.rst
index 3950583f2b1549b27f568632547e22e9ef8bc167..30799f734ca5568002d790c1db0ced7454bbbc8d 100644
--- a/Documentation/admin-guide/pm/cpufreq.rst
+++ b/Documentation/admin-guide/pm/cpufreq.rst
@@ -398,7 +398,9 @@ policy limits change after that.
This governor does not do anything by itself. Instead, it allows user space
to set the CPU frequency for the policy it is attached to by writing to the
-``scaling_setspeed`` attribute of that policy.
+``scaling_setspeed`` attribute of that policy. Though the intention may be to
+set an exact frequency for the policy, the actual frequency may vary depending
+on hardware coordination, thermal and power limits, and other factors.
``schedutil``
-------------
--
2.43.0
next prev parent reply other threads:[~2025-05-27 13:00 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 ` Shashank Balaji [this message]
2025-06-17 10:14 ` [PATCH v2 0/2] cpufreq: userspace: add " Shashank Balaji
2025-06-18 19:35 ` 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=20250527-userspace-governor-doc-v2-2-0e22c69920f2@sony.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®