From: Sumit Gupta <sumitg@nvidia.com>
To: <rafael@kernel.org>, <rui.zhang@intel.com>, <lenb@kernel.org>,
<treding@nvidia.com>, <jonathanh@nvidia.com>,
<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <sumitg@nvidia.com>, <sanjayc@nvidia.com>,
<ksitaraman@nvidia.com>, <srikars@nvidia.com>,
<jbrasen@nvidia.com>, <bbasu@nvidia.com>
Subject: [Patch 0/2] Add support for _TFP and configurable throttle pctg
Date: Thu, 17 Aug 2023 15:00:09 +0530 [thread overview]
Message-ID: <20230817093011.1378-1-sumitg@nvidia.com> (raw)
This patch set adds support for two features to get a finer control
over the impact of Thermal Throttling on performance.
1) Patch 1: Adds support to read Thermal fast Sampling Period (_TFP)
ACPI object and use it over "Thermal Sampling Period (_TSP)" for
Passive cooling if both are present.
2) Patch 2: Adds support to configure the CPUFREQ reduction percentage
and not always cause throttling in steps of "20%".
Both patches can be applied independently.
Jeff Brasen (1):
ACPI: thermal: Add Thermal fast Sampling Period (_TFP) support
Srikar Srimath Tirumala (1):
ACPI: processor: Add support to configure CPUFREQ reduction pctg
drivers/acpi/Kconfig | 15 +++++++++++++++
drivers/acpi/processor_thermal.c | 19 ++++++++++++++++---
drivers/acpi/thermal.c | 21 ++++++++++++++-------
3 files changed, 45 insertions(+), 10 deletions(-)
--
2.17.1
next reply other threads:[~2023-08-17 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 9:30 Sumit Gupta [this message]
2023-08-17 9:30 ` [Patch 1/2] ACPI: thermal: Add Thermal fast Sampling Period (_TFP) support Sumit Gupta
2023-08-18 18:33 ` Rafael J. Wysocki
2023-08-21 11:48 ` Sumit Gupta
2023-08-17 9:30 ` [Patch 2/2] ACPI: processor: Add support to configure CPUFREQ reduction pctg Sumit Gupta
2023-08-18 18:40 ` Rafael J. Wysocki
2023-08-21 13:24 ` Sumit Gupta
2023-08-21 17:09 ` Rafael J. Wysocki
2023-08-24 13:18 ` Sumit Gupta
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=20230817093011.1378-1-sumitg@nvidia.com \
--to=sumitg@nvidia.com \
--cc=bbasu@nvidia.com \
--cc=jbrasen@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=ksitaraman@nvidia.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sanjayc@nvidia.com \
--cc=srikars@nvidia.com \
--cc=treding@nvidia.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