From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rjw@rjwysocki.net, viresh.kumar@linaro.org
Cc: linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
ashwin.chaugule@linaro.org
Subject: Re: [PATCH 0/5] x86 CPPC usage
Date: Thu, 18 Aug 2016 14:14:20 -0700 [thread overview]
Message-ID: <1471554860.1602.17.camel@linux.intel.com> (raw)
In-Reply-To: <1470874646-70570-1-git-send-email-srinivas.pandruvada@linux.intel.com>
On Wed, 2016-08-10 at 17:17 -0700, Srinivas Pandruvada wrote:
> The x86 HWP (Hardware Controlled Performance States) is an
> implementation
> of the ACPI-defined Collaborative Processor Performance Control
> (CPPC).
> The current implementation of HWP doesn't use CPPC, but CPPC brings
> in
> some advanced features. So we will be submitting changes to use CPPC.
>
> The first series only contains ACPI CPPC changes required for x86.
>
Since I didn't see any major objection to this series, I will resubmit
these changes along with the use case of CPPC on x86 to support turbo
feature.
Thanks,
Srinivas
> Srinivas Pandruvada (5):
> acpi: cppc: Allow build with ACPI_CPU_FREQ_PSS config
> acpi: cpcc: Add integer read support
> acpi: cppc: Add support for function fixed hardware address
> acpi: cppc: Add prefix cppc to cpudata structure name
> acpi: bus: Enable HWP CPPC objects
>
> drivers/acpi/Kconfig | 1 -
> drivers/acpi/bus.c | 7 ++++
> drivers/acpi/cppc_acpi.c | 88
> +++++++++++++++++++++++++++++++++++------
> drivers/acpi/processor_driver.c | 5 ++-
> drivers/cpufreq/cppc_cpufreq.c | 14 +++----
> include/acpi/cppc_acpi.h | 4 +-
> 6 files changed, 95 insertions(+), 24 deletions(-)
>
prev parent reply other threads:[~2016-08-19 1:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 0:17 [PATCH 0/5] x86 CPPC usage Srinivas Pandruvada
2016-08-11 0:17 ` [PATCH 1/5] acpi: cppc: Allow build with ACPI_CPU_FREQ_PSS config Srinivas Pandruvada
2016-08-12 9:13 ` Alexey Klimov
2016-08-12 12:34 ` Srinivas Pandruvada
2016-08-12 16:04 ` Prakash, Prashanth
2016-08-12 16:32 ` Hoan Tran
2016-08-12 16:53 ` Srinivas Pandruvada
2016-08-12 16:35 ` Hoan Tran
2016-08-12 16:52 ` Srinivas Pandruvada
2016-08-12 16:58 ` Hoan Tran
2016-08-12 17:16 ` Srinivas Pandruvada
2016-08-11 0:17 ` [PATCH 2/5] acpi: cpcc: Add integer read support Srinivas Pandruvada
2016-08-11 0:17 ` [PATCH 3/5] acpi: cppc: Add support for function fixed hardware address Srinivas Pandruvada
2016-08-11 0:17 ` [PATCH 4/5] acpi: cppc: Add prefix cppc to cpudata structure name Srinivas Pandruvada
2016-08-11 0:17 ` [PATCH 5/5] acpi: bus: Enable HWP CPPC objects Srinivas Pandruvada
2016-08-16 14:32 ` Alexey Klimov
2016-08-16 16:50 ` Srinivas Pandruvada
2016-08-18 21:14 ` Srinivas Pandruvada [this message]
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=1471554860.1602.17.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=ashwin.chaugule@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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).