From: Roberto Ricci <io@r-ricci.it>
To: Thomas Renninger <trenn@suse.com>, Shuah Khan <shuah@kernel.org>,
"John B. Wyatt IV" <jwyatt@redhat.com>,
John Kacur <jkacur@redhat.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Roberto Ricci <io@r-ricci.it>
Subject: [PATCH v4 5/6] cpupower-frequency-info.1: document --boost and --epp options
Date: Tue, 24 Mar 2026 02:35:42 +0100 [thread overview]
Message-ID: <20260324013543.4776-6-io@r-ricci.it> (raw)
In-Reply-To: <20260324013543.4776-1-io@r-ricci.it>
`cpupower frequency-info` supports the '--boost' option since the program
was first added with commit 7fe2f6399a84 ("cpupowerutils - cpufrequtils
extended with quite some features"), but the man page lacks it.
'--epp' has been added with commit 5f567afc283f ("cpupower: Add support for
showing energy performance preference") but it has never been added to the
man page.
cpufreq-info.c:
{"boost", no_argument, NULL, 'b'},
...
{"epp", no_argument, NULL, 'z'},
Signed-off-by: Roberto Ricci <io@r-ricci.it>
---
tools/power/cpupower/man/cpupower-frequency-info.1 | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/tools/power/cpupower/man/cpupower-frequency-info.1 b/tools/power/cpupower/man/cpupower-frequency-info.1
index 7fce2b2e0506..346c2a6e40f4 100644
--- a/tools/power/cpupower/man/cpupower-frequency-info.1
+++ b/tools/power/cpupower/man/cpupower-frequency-info.1
@@ -32,6 +32,12 @@ Gets the currently used cpufreq policy.
\fB\-g\fR \fB\-\-governors\fR
Determines available cpufreq governors.
.TP
+\fB\-b\fR \fB\-\-boost\fR
+Gets the current boost state support.
+.TP
+\fB\-z\fR \fB\-\-epp\fR
+Gets the current EPP (energy performance preference).
+.TP
\fB\-r\fR \fB\-\-related\-cpus\fR
Determines which CPUs run at the same hardware frequency.
.TP
--
2.53.0
next prev parent reply other threads:[~2026-03-24 1:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 1:35 [PATCH v4 0/6] cpupower: fix various man pages issues Roberto Ricci
2026-03-24 1:35 ` [PATCH v4 1/6] cpupower-frequency-set.1: trim trailing whitespace Roberto Ricci
2026-03-24 19:59 ` Shuah Khan
2026-03-24 22:08 ` Roberto Ricci
2026-03-24 1:35 ` [PATCH v4 2/6] cpupower-idle-info.1: fix short option names Roberto Ricci
2026-03-24 1:35 ` [PATCH v4 3/6] cpupower-frequency-info.1: trim trailing whitespace Roberto Ricci
2026-03-24 20:00 ` Shuah Khan
2026-03-24 22:04 ` Roberto Ricci
2026-03-24 22:09 ` Shuah Khan
2026-03-24 1:35 ` [PATCH v4 4/6] cpupower-frequency-info.1: use the proper name of the --perf option Roberto Ricci
2026-03-24 1:35 ` Roberto Ricci [this message]
2026-03-24 1:35 ` [PATCH v4 6/6] cpupower-info.1: describe the --perf-bias option Roberto Ricci
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=20260324013543.4776-6-io@r-ricci.it \
--to=io@r-ricci.it \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=trenn@suse.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
all inboxes | Powered by JetHome®