X86 platform drivers
 help / color / mirror / Atom feed
From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "hdegoede@redhat.com" <hdegoede@redhat.com>,
	"mgross@linux.intel.com" <mgross@linux.intel.com>
Cc: "srinivas.pandruvada@linux.intel.com" 
	<srinivas.pandruvada@linux.intel.com>,
	"prarit@redhat.com" <prarit@redhat.com>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>
Subject: [GIT PULL]: tools/power/x86/intel-speed-select pull request for 6.3-rc1
Date: Thu, 19 Jan 2023 19:08:45 +0000	[thread overview]
Message-ID: <46c25f3c9426d038ca773da56a273a03e237dc23.camel@intel.com> (raw)

Hi Hans,

This release adds following change:
    - Minor fixes for coverity static analysis
    - Don't read cpufreq on offline CPUs
    - SST turbo-freq enable on auto mode when user disables SMT from
    kernel command line
    - Fix uncore frequency display
    - Set uncore frequency max/min limits on perf level change

Changes on top of
https://kernel.googlesource.com/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86
review-hans

The following changes since commit
c6a41c14a9691ff356b7d3e0d8da3f9afd4b72cc:

  platform/x86: intel: punit_ipc: Drop empty platform remove function
(2023-01-16 17:32:22 +0100)

are available in the Git repository at:

  https://github.com/spandruvada/linux-kernel.git intel-sst

for you to fetch changes up to
153c05bfda9914c721171b6aad35499f1507c83f:

  tools/power/x86/intel-speed-select: v1.14 release (2023-01-18
17:25:34 -0800)

----------------------------------------------------------------
Srinivas Pandruvada (5):
      tools/power/x86/intel-speed-select: cpufreq reads on offline CPUs
      tools/power/x86/intel-speed-select: turbo-freq auto mode with SMT
off
      tools/power intel-speed-select: Fix display of uncore min
frequency
      tools/power/x86/intel-speed-select: Adjust uncore max/min
frequency
      tools/power/x86/intel-speed-select: v1.14 release

Zhang Rui (6):
      tools/power/x86/intel-speed-select: Remove wrong check in
set_isst_id()
      tools/power/x86/intel-speed-select: Remove unused non_block flag
      tools/power/x86/intel-speed-select: Handle open() failure case
      tools/power/x86/intel-speed-select: Remove duplicate dup()
      tools/power/x86/intel-speed-select: Use null-terminated string
      tools/power/x86/intel-speed-select: Add Emerald Rapid quirk

 tools/power/x86/intel-speed-select/hfi-events.c   |  4 ----
 tools/power/x86/intel-speed-select/isst-config.c  | 82
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----
 tools/power/x86/intel-speed-select/isst-core.c    | 24
+++++++++++++++++++
 tools/power/x86/intel-speed-select/isst-daemon.c  |  3 +--
 tools/power/x86/intel-speed-select/isst-display.c | 11 +++++++--
 tools/power/x86/intel-speed-select/isst.h         |  4 ++++
 6 files changed, 116 insertions(+), 12 deletions(-)

             reply	other threads:[~2023-01-19 19:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 19:08 Pandruvada, Srinivas [this message]
2023-01-30 13:57 ` [GIT PULL]: tools/power/x86/intel-speed-select pull request for 6.3-rc1 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=46c25f3c9426d038ca773da56a273a03e237dc23.camel@intel.com \
    --to=srinivas.pandruvada@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=mgross@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    /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