From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: corbet@lwn.net, lenb@kernel.org, viresh.kumar@linaro.org,
robert.moore@intel.com, erik.schmauss@intel.com,
juri.lelli@redhat.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-pm@vger.kernel.org, devel@acpica.org,
pprakash@codeaurora.org, george.cherian@cavium.com
Subject: Re: [PATCH v4 0/3] cpufreq: intel_pstate: Base frequency attribute
Date: Fri, 19 Oct 2018 12:17:24 +0200 [thread overview]
Message-ID: <2009466.qjoMG8mNOh@aspire.rjw.lan> (raw)
In-Reply-To: <20181015173721.66147-1-srinivas.pandruvada@linux.intel.com>
On Monday, October 15, 2018 7:37:18 PM CEST Srinivas Pandruvada wrote:
> This series presents base frequency to cpufreq sysfs when intel_pstate
> is in use in HWP mode.
>
> Changes:
> v4:
> - Documentation update only as suggested by Rafael
>
> v3:
> - Update documentation
> v2
> - Removed guaranteed attribute addition to acpi_cppc sysfs
> - Using the cppc_acpi interface to get base frequency and present
>
> Srinivas Pandruvada (3):
> ACPI / CPPC: Add support for guaranteed performance
> cpufreq: intel_pstate: Add base_frequency attribute
> Documentation: intel_pstate: Add base_frequency information
>
> Documentation/admin-guide/pm/intel_pstate.rst | 7 ++++
> drivers/acpi/cppc_acpi.c | 8 +++-
> drivers/cpufreq/intel_pstate.c | 38 +++++++++++++++++++
> include/acpi/cppc_acpi.h | 1 +
> 4 files changed, 52 insertions(+), 2 deletions(-)
>
>
All three applied, thanks!
prev parent reply other threads:[~2018-10-19 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 17:37 Srinivas Pandruvada
2018-10-15 17:37 ` [PATCH v4 1/3] ACPI / CPPC: Add support for guaranteed performance Srinivas Pandruvada
2018-10-15 17:37 ` [PATCH v4 2/3] cpufreq: intel_pstate: Add base_frequency attribute Srinivas Pandruvada
2018-10-15 17:37 ` [PATCH v4 3/3] Documentation: intel_pstate: Add base_frequency information Srinivas Pandruvada
2018-10-19 10:17 ` Rafael J. Wysocki [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=2009466.qjoMG8mNOh@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=corbet@lwn.net \
--cc=devel@acpica.org \
--cc=erik.schmauss@intel.com \
--cc=george.cherian@cavium.com \
--cc=juri.lelli@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pprakash@codeaurora.org \
--cc=robert.moore@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--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
all inboxes | Powered by JetHome®