From: "Prakash, Prashanth" <pprakash@codeaurora.org>
To: ahs3@redhat.com, linux-acpi@vger.kernel.org
Cc: rjw@rjwysocki.net, alexey.klimov@arm.com, hotran@apm.com,
cov@codeaurora.org
Subject: Re: [PATCH 0/2] additional sysfs entries for CPPC
Date: Thu, 5 Jan 2017 10:59:11 -0700 [thread overview]
Message-ID: <502822f6-9983-506e-df9d-34aca752382f@codeaurora.org> (raw)
In-Reply-To: <b147a3c2-5435-84b2-f3ff-6fb96e764fd5@redhat.com>
On 1/3/2017 11:37 AM, Al Stone wrote:
> On 12/14/2016 06:06 PM, Prashanth Prakash wrote:
>> 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.
>>
>> Prashanth Prakash (2):
>> ACPI / CPPC: read all perf caps in a single cppc read command
>> ACPI / CPPC: add sysfs entries for CPPC perf capabilities
>>
>> drivers/acpi/cppc_acpi.c | 164 ++++++++++++++++++++++++++++++-----------------
>> include/acpi/cppc_acpi.h | 3 +-
>> 2 files changed, 107 insertions(+), 60 deletions(-)
>>
> Nice addition, Prashanth. I had thought about doing this, but got distracted.
> Thanks for following through :). I have not had a chance to test these yet, but
> will do so as soon as I can; my initial review is pretty positive, though.
>
Thanks Al! I look forward for your test results.
Thanks,
Prashanth
next prev parent reply other threads:[~2017-01-05 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 1:06 [PATCH 0/2] additional sysfs entries for CPPC Prashanth Prakash
2016-12-15 1:06 ` [PATCH 1/2] ACPI / CPPC: read all perf caps in a single cppc read command Prashanth Prakash
2016-12-15 1:06 ` [PATCH 2/2] ACPI / CPPC: add sysfs entries for CPPC perf capabilities Prashanth Prakash
2017-01-03 18:37 ` [PATCH 0/2] additional sysfs entries for CPPC Al Stone
2017-01-05 17:59 ` Prakash, Prashanth [this message]
2017-02-08 22:10 ` Al Stone
2017-02-09 0:44 ` Rafael J. Wysocki
2017-02-13 16:38 ` Prakash, Prashanth
2017-03-03 18:32 ` Prakash, Prashanth
2017-03-24 16:34 ` Prakash, Prashanth
2017-03-25 13:32 ` Rafael J. Wysocki
2017-03-27 17:00 ` Prakash, Prashanth
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=502822f6-9983-506e-df9d-34aca752382f@codeaurora.org \
--to=pprakash@codeaurora.org \
--cc=ahs3@redhat.com \
--cc=alexey.klimov@arm.com \
--cc=cov@codeaurora.org \
--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