From: Hanjun Guo <guohanjun@huawei.com>
To: Sumit Gupta <sumitg@nvidia.com>,
"Rafael J. Wysocki" <rafael@kernel.org>, <lpieralisi@kernel.org>,
<sudeep.holla@arm.com>
Cc: <rui.zhang@intel.com>, <lenb@kernel.org>,
<linux-acpi@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <treding@nvidia.com>,
<jonathanh@nvidia.com>, <bbasu@nvidia.com>, <sanjayc@nvidia.com>,
<ksitaraman@nvidia.com>, <srikars@nvidia.com>,
<jbrasen@nvidia.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [Patch v5 2/2] ACPI: processor: reduce CPUFREQ thermal reduction pctg for Tegra241
Date: Thu, 9 Nov 2023 15:50:31 +0800 [thread overview]
Message-ID: <7f17a560-f26a-eae5-f8d5-1f6602ed8f7c@huawei.com> (raw)
In-Reply-To: <4fd879be-ae89-45a7-9607-b55606cfb3ac@nvidia.com>
On 2023/10/20 16:30, Sumit Gupta wrote:
>
>>> Current implementation of processor_thermal performs software throttling
>>> in fixed steps of "20%" which can be too coarse for some platforms.
>>> We observed some performance gain after reducing the throttle
>>> percentage.
>>> Change the CPUFREQ thermal reduction percentage and maximum thermal
>>> steps
>>> to be configurable. Also, update the default values of both for Nvidia
>>> Tegra241 (Grace) SoC. The thermal reduction percentage is reduced to
>>> "5%"
>>> and accordingly the maximum number of thermal steps are increased as
>>> they
>>> are derived from the reduction percentage.
>>>
>>> Signed-off-by: Srikar Srimath Tirumala <srikars@nvidia.com>
>>> Co-developed-by: Sumit Gupta <sumitg@nvidia.com>
>>> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
>>> ---
>>> drivers/acpi/arm64/Makefile | 1 +
>>> drivers/acpi/arm64/thermal_cpufreq.c | 20 ++++++++++++++++
>>> drivers/acpi/processor_thermal.c | 35 +++++++++++++++++++++++++---
>>> include/linux/acpi.h | 9 +++++++
>>> 4 files changed, 62 insertions(+), 3 deletions(-)
>>> create mode 100644 drivers/acpi/arm64/thermal_cpufreq.c
>>>
>>> diff --git a/drivers/acpi/arm64/Makefile b/drivers/acpi/arm64/Makefile
>>> index 143debc1ba4a..3f181d8156cc 100644
>>> --- a/drivers/acpi/arm64/Makefile
>>> +++ b/drivers/acpi/arm64/Makefile
>>> @@ -5,3 +5,4 @@ obj-$(CONFIG_ACPI_GTDT) += gtdt.o
>>> obj-$(CONFIG_ACPI_APMT) += apmt.o
>>> obj-$(CONFIG_ARM_AMBA) += amba.o
>>> obj-y += dma.o init.o
>>> +obj-$(CONFIG_ACPI) += thermal_cpufreq.o
>>> diff --git a/drivers/acpi/arm64/thermal_cpufreq.c
>>> b/drivers/acpi/arm64/thermal_cpufreq.c
>>> new file mode 100644
>>> index 000000000000..de834fb013e7
>>> --- /dev/null
>>> +++ b/drivers/acpi/arm64/thermal_cpufreq.c
>>> @@ -0,0 +1,20 @@
>>> +// SPDX-License-Identifier: GPL-2.0-only
>>> +#include <linux/acpi.h>
>>> +
>>> +#ifdef CONFIG_HAVE_ARM_SMCCC_DISCOVERY
>>> +#define SMCCC_SOC_ID_T241 0x036b0241
>>> +
>>> +int acpi_thermal_cpufreq_pctg(void)
>>> +{
>>> + s32 soc_id = arm_smccc_get_soc_id_version();
>>> +
>>> + /*
>>> + * Check JEP106 code for NVIDIA Tegra241 chip (036b:0241) and
>>> + * reduce the CPUFREQ Thermal reduction percentage to 5%.
>>> + */
>>> + if (soc_id == SMCCC_SOC_ID_T241)
>>> + return 5;
>>> +
>>> + return 0;
>>> +}
>>> +#endif
>>
>> This part needs an ACK from the ARM folks.
>>
> Sorry, missed adding 'ACPI arm64' maintainers. Added Lorenzo, Sudeep and
> Hanjun.
Sorry for the late reply, would mind giving me the link which the ID
(SMCCC_SOC_ID_T241) is documented?
Thanks
Hanjun
next prev parent reply other threads:[~2023-11-09 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 10:54 [Patch v5 0/2] Add support for _TFP and change throttle pctg Sumit Gupta
2023-10-14 10:54 ` [Patch v5 1/2] ACPI: thermal: Add Thermal fast Sampling Period (_TFP) support Sumit Gupta
2023-10-18 11:48 ` Rafael J. Wysocki
2023-10-19 18:30 ` Sumit Gupta
2023-10-14 10:54 ` [Patch v5 2/2] ACPI: processor: reduce CPUFREQ thermal reduction pctg for Tegra241 Sumit Gupta
2023-10-18 13:04 ` Rafael J. Wysocki
2023-10-20 8:30 ` Sumit Gupta
2023-11-09 7:50 ` Hanjun Guo [this message]
2023-11-09 11:36 ` Sumit Gupta
2023-10-23 8:53 ` Sudeep Holla
2023-10-25 12:51 ` 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=7f17a560-f26a-eae5-f8d5-1f6602ed8f7c@huawei.com \
--to=guohanjun@huawei.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-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sanjayc@nvidia.com \
--cc=srikars@nvidia.com \
--cc=sudeep.holla@arm.com \
--cc=sumitg@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