mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rafael@kernel.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	daniel.lezcano@linaro.org, rui.zhang@intel.com,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	kernel test robot <lkp@intel.com>
Subject: [PATCH v5 0/4] Use idle_inject framework for intel_powerclamp
Date: Wed,  1 Feb 2023 10:28:50 -0800	[thread overview]
Message-ID: <20230201182854.2158535-1-srinivas.pandruvada@linux.intel.com> (raw)

Dropped the per core idle injection patch from this series. Hence the
subject of this series is changed. Now it is just for using
idle inject framework for intel_powerclamp.
Add additionl patch for module paramters to set cpumask and max idle percent.

The old cover letter:
This series introduces per CPU idle injection. In preparation for this
enhance the existing powercap/idle_inject and modify intel_powerclamp
to use this. Then add per core idle injection driver.

v5:
- additionl patch for module paramters to set cpumask and max idle percent
- One fix for update callback
- Rebased on top of patch 
 "thermal: intel_powerclamp: Fix cur_state for multi package system"

v4:
- Dropped the per core idle inject patch

v3
- Change callback from per CPU to per device and use in intel_powerclamp
- Remove unused var in per cpu idle injection module

v2
- Update based on feedback from Rafael on patch 2/4
- Kconfig dependency issue
Reported-by: kernel test robot <lkp@intel.com>

Srinivas Pandruvada (4):
  powercap: idle_inject: Export symbols
  powercap: idle_inject: Add update callback
  thermal/drivers/intel_powerclamp: Use powercap idle-inject framework
  thermal/drivers/intel_powerclamp: Add additional module params

 .../driver-api/thermal/intel_powerclamp.rst   |  22 +
 drivers/powercap/idle_inject.c                |  57 +-
 drivers/thermal/intel/Kconfig                 |   2 +
 drivers/thermal/intel/intel_powerclamp.c      | 512 ++++++++++--------
 include/linux/idle_inject.h                   |   3 +
 5 files changed, 367 insertions(+), 229 deletions(-)

-- 
2.39.1


             reply	other threads:[~2023-02-01 18:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 18:28 Srinivas Pandruvada [this message]
2023-02-01 18:28 ` [PATCH v5 1/4] powercap: idle_inject: Export symbols Srinivas Pandruvada
2023-02-02 13:48   ` Daniel Lezcano
2023-02-01 18:28 ` [PATCH v5 2/4] powercap: idle_inject: Add update callback Srinivas Pandruvada
2023-02-01 18:28 ` [PATCH v5 3/4] thermal/drivers/intel_powerclamp: Use powercap idle-inject framework Srinivas Pandruvada
2023-02-01 18:28 ` [PATCH v5 4/4] thermal/drivers/intel_powerclamp: Add additional module params Srinivas Pandruvada
2023-02-02 16:41   ` Rafael J. Wysocki
2023-02-04  5:29     ` srinivas pandruvada
2023-02-04 17:46   ` Zhang, Rui
2023-02-05  3:01     ` srinivas pandruvada
2023-02-02 16:20 ` [PATCH v5 0/4] Use idle_inject framework for intel_powerclamp 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=20230201182854.2158535-1-srinivas.pandruvada@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@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

all inboxes | Powered by JetHome®