From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: corbet@lwn.net, rjw@rjwysocki.net, lenb@kernel.org,
viresh.kumar@linaro.org, robert.moore@intel.com,
erik.schmauss@intel.com
Cc: 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,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH v3 0/3] cpufreq: intel_pstate: Base frequency attribute
Date: Fri, 12 Oct 2018 09:43:57 -0700 [thread overview]
Message-ID: <20181012164400.3479-1-srinivas.pandruvada@linux.intel.com> (raw)
This series presents base frequency to cpufreq sysfs when intel_pstate
is in use in HWP mode.
Changes:
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 | 4 ++
drivers/acpi/cppc_acpi.c | 8 +++-
drivers/cpufreq/intel_pstate.c | 38 +++++++++++++++++++
include/acpi/cppc_acpi.h | 1 +
4 files changed, 49 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-12 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 16:43 Srinivas Pandruvada [this message]
2018-10-12 16:43 ` [PATCH v3 1/3] ACPI / CPPC: Add support for guaranteed performance Srinivas Pandruvada
2018-10-12 16:43 ` [PATCH v3 2/3] cpufreq: intel_pstate: Add base_frequency attribute Srinivas Pandruvada
2018-10-12 16:44 ` [PATCH v3 3/3] Documentation: intel_pstate: Add base_frequency information Srinivas Pandruvada
2018-10-15 8:53 ` Rafael J. Wysocki
2018-10-15 15:49 ` Srinivas Pandruvada
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=20181012164400.3479-1-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--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=rjw@rjwysocki.net \
--cc=robert.moore@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;
as well as URLs for NNTP newsgroup(s).