From: Prashanth Prakash <pprakash@codeaurora.org>
To: linux-acpi@vger.kernel.org
Cc: rjw@rjwysocki.net, hotran@apm.com, ahs3@redhat.com,
Prashanth Prakash <pprakash@codeaurora.org>
Subject: [PATCH V2 0/2] additional sysfs entries for CPPC
Date: Wed, 29 Mar 2017 13:49:58 -0600 [thread overview]
Message-ID: <1490817000-13876-1-git-send-email-pprakash@codeaurora.org> (raw)
This patch-set adds few additional sysfs entries to expose the
performance capabilities of each CPU. The performance capabilities
include highest perf, lowest perf, nominal perf and lowest
non-linear perf. See 8.4.7.1 for ACPI 6.1 spec for details on
these capabilities.
cppc_cpufreq driver operates in KHz scale whereas the delivered
performance computed in userspace will be in abstract CPPC scale, so
exposing perf capabilities should allow userspace to figure out the
conversion factor from CPPC scale to KHz.
Changes in V2:
- Removed caching of perf caps based on Rafael's inputs
Prashanth Prakash (2):
ACPI / CPPC: Read lowest non linear perf in cppc_get_perf_caps
ACPI / CPPC: add sysfs entries for CPPC perf capabilities
drivers/acpi/cppc_acpi.c | 80 ++++++++++++++++++++++++++----------------------
include/acpi/cppc_acpi.h | 3 +-
2 files changed, 46 insertions(+), 37 deletions(-)
--
Qualcomm Datacenter Technologies on behalf of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next reply other threads:[~2017-03-29 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 19:49 Prashanth Prakash [this message]
2017-03-29 19:49 ` [PATCH V2 1/2] ACPI / CPPC: Read lowest non linear perf in cppc_get_perf_caps Prashanth Prakash
2017-04-18 14:28 ` Rafael J. Wysocki
2017-04-18 17:03 ` Prakash, Prashanth
2017-03-29 19:50 ` [PATCH V2 2/2] ACPI / CPPC: add sysfs entries for CPPC perf capabilities Prashanth Prakash
2017-04-17 15:42 ` [PATCH V2 0/2] additional sysfs entries for CPPC Prakash, Prashanth
2017-04-17 16:20 ` 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=1490817000-13876-1-git-send-email-pprakash@codeaurora.org \
--to=pprakash@codeaurora.org \
--cc=ahs3@redhat.com \
--cc=hotran@apm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).