From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rafael@kernel.org, rui.zhang@intel.com, daniel.lezcano@linaro.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH v4 0/3] Use idle_inject framework for intel_powerclamp
Date: Fri, 27 Jan 2023 12:20:45 -0800 [thread overview]
Message-ID: <20230127202048.992504-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.
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.
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 (3):
powercap: idle_inject: Export symbols
powercap: idle_inject: Add update callback
thermal/drivers/intel_powerclamp: Use powercap idle-inject framework
drivers/powercap/idle_inject.c | 57 +++-
drivers/thermal/intel/Kconfig | 2 +
drivers/thermal/intel/intel_powerclamp.c | 374 ++++++++++-------------
include/linux/idle_inject.h | 3 +
4 files changed, 209 insertions(+), 227 deletions(-)
--
2.37.2
next reply other threads:[~2023-01-27 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 20:20 Srinivas Pandruvada [this message]
2023-01-27 20:20 ` [PATCH v4 1/3] powercap: idle_inject: Export symbols Srinivas Pandruvada
2023-01-27 20:20 ` [PATCH v4 2/3] powercap: idle_inject: Add update callback Srinivas Pandruvada
2023-01-27 20:20 ` [PATCH v4 3/3] thermal/drivers/intel_powerclamp: Use powercap idle-inject framework 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=20230127202048.992504-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®