From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Ashwin Chaugule <ashwin.chaugule@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: dirk.brandewie@gmail.com,
"rwells@codeaurora.org" <rwells@codeaurora.org>,
Linda Knippers <linda.knippers@hp.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Patch Tracking <patches@linaro.org>,
"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>
Subject: Re: [PATCH v3 1/2] CPPC as a PID controller backend
Date: Mon, 01 Dec 2014 06:56:17 -0800 [thread overview]
Message-ID: <547C8191.4030002@gmail.com> (raw)
In-Reply-To: <CAKohpomTpDO4mRvivYpm5xLSpOniO_iw0n7Rj4pCksjBim-cRg@mail.gmail.com>
On 11/30/2014 10:26 PM, Viresh Kumar wrote:
> On 1 December 2014 at 11:53, Ashwin Chaugule <ashwin.chaugule@linaro.org> wrote:
>> On 19 November 2014 at 15:36, Ashwin Chaugule
>> <ashwin.chaugule@linaro.org> wrote:
>>> CPPC (Collaborative Processor Performance Control) is defined
>>> in the ACPI 5.0+ spec. It is a method for controlling CPU
>>> performance on a continuous scale using performance feedback
>>> registers. In contrast to the legacy "pstate" scale which is
>>> discretized, and tied to CPU frequency, CPPC works off of an
>>> abstract continuous scale. This lets the platforms freely interpret
>>> the abstract unit and optimize it for power and performance given
>>> its knowledge of thermal budgets and other constraints.
>>>
>>> The PID governor operates on similar concepts and can use CPPC
>>> semantics to acquire the information it needs. This information
>>> may be provided by various platforms via MSRs, CP15s or memory
>>> mapped registers. CPPC helps to wrap all these variations into a
>>> common framework.
>>>
>>> This patch introduces CPPC using PID as its governor for CPU
>>> performance management.
>>>
>>> Signed-off-by: Ashwin Chaugule <ashwin.chaugule@linaro.org>
>>> ---
>>> drivers/cpufreq/Kconfig | 12 +
>>> drivers/cpufreq/Makefile | 1 +
>>> drivers/cpufreq/acpi_pid.c | 1156 ++++++++++++++++++++++++++++++++++++++++++++
>>> 3 files changed, 1169 insertions(+)
>>> create mode 100644 drivers/cpufreq/acpi_pid.c
>>
>>
>> Ping.
>>
>> Any comments on these patches?
>
> Redirecting the Ping to Rafael/Dirk :)
>
Ashwin has incorporated my feedback. I have no issues
--Dirk
next prev parent reply other threads:[~2014-12-01 14:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 20:36 [PATCH v3 0/2] CPPC as a PID backend Ashwin Chaugule
2014-11-19 20:36 ` [PATCH v3 1/2] CPPC as a PID controller backend Ashwin Chaugule
2014-12-01 6:23 ` Ashwin Chaugule
2014-12-01 6:26 ` Viresh Kumar
2014-12-01 14:56 ` Dirk Brandewie [this message]
2014-12-15 14:42 ` Ashwin Chaugule
2014-12-15 15:16 ` Rafael J. Wysocki
2014-12-21 0:14 ` Ashwin Chaugule
2014-12-22 22:43 ` Rafael J. Wysocki
2014-12-15 15:21 ` Rafael J. Wysocki
2014-12-15 15:22 ` Ashwin Chaugule
2014-11-19 20:36 ` [PATCH v3 2/2] ACPI PID: Add frequency domain awareness Ashwin Chaugule
2014-11-19 20:39 ` [PATCH v3 0/2] CPPC as a PID backend Ashwin Chaugule
-- strict thread matches above, loose matches on Subject: below --
2014-11-19 20:34 Ashwin Chaugule
2014-11-19 20:34 ` [PATCH v3 1/2] CPPC as a PID controller backend Ashwin Chaugule
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=547C8191.4030002@gmail.com \
--to=dirk.brandewie@gmail.com \
--cc=Catalin.Marinas@arm.com \
--cc=ashwin.chaugule@linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linda.knippers@hp.com \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=rwells@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).