public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: rafael.j.wysocki@intel.com
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	srinivas.pandruvada@intel.com
Subject: [PATCH 0/3] Add RAPL/DPTF support for Pantherlake
Date: Tue,  3 Dec 2024 15:57:59 +0800	[thread overview]
Message-ID: <20241203075802.584741-1-rui.zhang@intel.com> (raw)

There is an effort on going to avoid per CPU model ID enabling for RAPL
support. But this takes some time and requires sufficient test to make
sure no regression introduced. So enable PantherLake RAPL support before
any rework.

Zhang Rui (3):
  powercap: intel_rapl: Add support for PantherLake platform
  thermal: intel: int340x: processor: Enable MMIO RAPL for PantherLake
  ACPI: DPTF: Support Panther Lake

 drivers/acpi/dptf/dptf_pch_fivr.c                           | 1 +
 drivers/acpi/dptf/dptf_power.c                              | 2 ++
 drivers/acpi/dptf/int340x_thermal.c                         | 6 ++++++
 drivers/acpi/fan.h                                          | 1 +
 drivers/powercap/intel_rapl_common.c                        | 1 +
 drivers/thermal/intel/int340x_thermal/int3400_thermal.c     | 1 +
 drivers/thermal/intel/int340x_thermal/int3403_thermal.c     | 1 +
 .../intel/int340x_thermal/processor_thermal_device.h        | 1 +
 .../intel/int340x_thermal/processor_thermal_device_pci.c    | 1 +
 9 files changed, 15 insertions(+)

-- 
2.43.0


             reply	other threads:[~2024-12-03  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03  7:57 Zhang Rui [this message]
2024-12-03  7:58 ` [PATCH 1/3] powercap: intel_rapl: Add support for PantherLake platform Zhang Rui
2024-12-03  7:58 ` [PATCH 2/3] thermal: intel: int340x: processor: Enable MMIO RAPL for PantherLake Zhang Rui
2024-12-03  7:58 ` [PATCH 3/3] ACPI: DPTF: Support Panther Lake Zhang Rui
2024-12-10 19:02 ` [PATCH 0/3] Add RAPL/DPTF support for Pantherlake Rafael J. Wysocki

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=20241203075802.584741-1-rui.zhang@intel.com \
    --to=rui.zhang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=srinivas.pandruvada@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