From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: hdegoede@redhat.com, markgross@kernel.org
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH 0/4] platform/x86/intel/uncore-freq: Enhance HW interface
Date: Thu, 3 Feb 2022 16:03:02 -0800 [thread overview]
Message-ID: <20220204000306.2517447-1-srinivas.pandruvada@linux.intel.com> (raw)
The uncore frequency scaling is getting used by more customers to either
have a deterministic performance or control power consumption.
The uncore frequency scaling depends on non architecture MSRs, format of
those MSR can be different on different generations of CPUs.
This series prepares for easy addition of new HW interface.
There are no functional changes done except adding a new addition to
read uncore frequency.
- The first patch creates a separate folder for uncore-freq.
- The second patch uses sysfs groups to create attributes.
- The third patch adds capability to read current uncore frequency.
- The fourth patch splits common and enumeration part. The enumeration
part will be specific to each HW interface.
Srinivas Pandruvada (4):
platform/x86/intel/uncore-freq: Move to uncore-frequency folder
platform/x86/intel/uncore-freq: Use sysfs API to create attributes
platform/x86/intel/uncore-freq: Display uncore current frequency
platform/x86/intel-uncore-freq: Split common and enumeration part
drivers/platform/x86/intel/Kconfig | 14 +-
drivers/platform/x86/intel/Makefile | 4 +-
drivers/platform/x86/intel/uncore-frequency.c | 452 ------------------
.../x86/intel/uncore-frequency/Kconfig | 21 +
.../x86/intel/uncore-frequency/Makefile | 9 +
.../uncore-frequency-common.c | 252 ++++++++++
.../uncore-frequency-common.h | 62 +++
.../intel/uncore-frequency/uncore-frequency.c | 272 +++++++++++
8 files changed, 620 insertions(+), 466 deletions(-)
delete mode 100644 drivers/platform/x86/intel/uncore-frequency.c
create mode 100644 drivers/platform/x86/intel/uncore-frequency/Kconfig
create mode 100644 drivers/platform/x86/intel/uncore-frequency/Makefile
create mode 100644 drivers/platform/x86/intel/uncore-frequency/uncore-frequency-common.c
create mode 100644 drivers/platform/x86/intel/uncore-frequency/uncore-frequency-common.h
create mode 100644 drivers/platform/x86/intel/uncore-frequency/uncore-frequency.c
--
2.31.1
next reply other threads:[~2022-02-04 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 0:03 Srinivas Pandruvada [this message]
2022-02-04 0:03 ` [PATCH 1/4] platform/x86/intel/uncore-freq: Move to uncore-frequency folder Srinivas Pandruvada
2022-02-04 0:03 ` [PATCH 2/4] platform/x86/intel/uncore-freq: Use sysfs API to create attributes Srinivas Pandruvada
2022-02-04 0:03 ` [PATCH 3/4] platform/x86/intel/uncore-freq: Display uncore current frequency Srinivas Pandruvada
2022-02-04 0:03 ` [PATCH 4/4] platform/x86/intel-uncore-freq: Split common and enumeration part Srinivas Pandruvada
2022-02-17 12:25 ` [PATCH 0/4] platform/x86/intel/uncore-freq: Enhance HW interface Hans de Goede
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=20220204000306.2517447-1-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.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