From: Sumit Gupta <sumitg@nvidia.com>
To: kernel test robot <lkp@intel.com>, <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>, <linux-tegra@vger.kernel.org>
Cc: <oe-kbuild-all@lists.linux.dev>, <sanjayc@nvidia.com>,
<ksitaraman@nvidia.com>, <srikars@nvidia.com>,
<jbrasen@nvidia.com>, <bbasu@nvidia.com>,
Sumit Gupta <sumitg@nvidia.com>
Subject: Re: [Patch v2 2/2] ACPI: processor: reduce CPUFREQ thermal reduction pctg for Tegra241
Date: Tue, 19 Sep 2023 16:57:09 +0530 [thread overview]
Message-ID: <c180c1e9-c15c-b4e2-678a-35a388a4a613@nvidia.com> (raw)
In-Reply-To: <202309140915.2J9OzWIZ-lkp@intel.com>
> Hi Sumit,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on rafael-pm/linux-next]
> [also build test WARNING on linus/master v6.6-rc1 next-20230913]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Sumit-Gupta/ACPI-thermal-Add-Thermal-fast-Sampling-Period-_TFP-support/20230914-004929
> base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
> patch link: https://lore.kernel.org/r/20230913164659.9345-3-sumitg%40nvidia.com
> patch subject: [Patch v2 2/2] ACPI: processor: reduce CPUFREQ thermal reduction pctg for Tegra241
> config: i386-defconfig (https://download.01.org/0day-ci/archive/20230914/202309140915.2J9OzWIZ-lkp@intel.com/config)
> compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230914/202309140915.2J9OzWIZ-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202309140915.2J9OzWIZ-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
>>> drivers/acpi/processor_thermal.c:141:6: warning: no previous declaration for 'acpi_thermal_cpufreq_config_nvidia' [-Wmissing-declarations]
> void acpi_thermal_cpufreq_config_nvidia(void)
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
Thank you for the report.
The below change fixes the warning for me.
-void acpi_thermal_cpufreq_config_nvidia(void)
+static void acpi_thermal_cpufreq_config_nvidia(void)
Hi Rafael,
If there is no other comment. Could you please add the change while
applying or you prefer me sending new version ?
Thank you,
Sumit Gupta
>
> vim +/acpi_thermal_cpufreq_config_nvidia +141 drivers/acpi/processor_thermal.c
>
> 140
> > 141 void acpi_thermal_cpufreq_config_nvidia(void)
> 142 {
> 143 #ifdef CONFIG_HAVE_ARM_SMCCC_DISCOVERY
> 144 s32 soc_id = arm_smccc_get_soc_id_version();
> 145
> 146 /* Check JEP106 code for NVIDIA Tegra241 chip (036b:0241) */
> 147 if ((soc_id < 0) || (soc_id != SMCCC_SOC_ID_T241))
> 148 return;
> 149
> 150 /* Reduce the CPUFREQ Thermal reduction percentage to 5% */
> 151 cpufreq_thermal_pctg = 5;
> 152
> 153 /*
> 154 * Derive the MAX_STEP from minimum throttle percentage so that the reduction
> 155 * percentage doesn't end up becoming negative. Also, cap the MAX_STEP so that
> 156 * the CPU performance doesn't become 0.
> 157 */
> 158 cpufreq_thermal_max_step = ((100 / cpufreq_thermal_pctg) - 1);
> 159 #endif
> 160 }
> 161
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-19 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 16:46 [Patch v2 0/2] Add support for _TFP and change throttle pctg Sumit Gupta
2023-09-13 16:46 ` [Patch v2 1/2] ACPI: thermal: Add Thermal fast Sampling Period (_TFP) support Sumit Gupta
2023-09-13 16:46 ` [Patch v2 2/2] ACPI: processor: reduce CPUFREQ thermal reduction pctg for Tegra241 Sumit Gupta
2023-09-14 2:09 ` kernel test robot
2023-09-19 11:27 ` Sumit Gupta [this message]
2023-09-19 13:54 ` Rafael J. Wysocki
2023-09-19 16:59 ` Sumit Gupta
2023-09-14 2:51 ` kernel test robot
2023-09-14 4:39 ` kernel test robot
2023-10-03 19:37 ` Rafael J. Wysocki
2023-10-06 15:14 ` 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=c180c1e9-c15c-b4e2-678a-35a388a4a613@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=linux-tegra@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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