From: Viresh Kumar <viresh.kumar@linaro.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
Yi-Wei Wang <yiweiw@nvidia.com>
Subject: Re: [PATCH] cpufreq: tegra194: Enable CPUFREQ thermal cooling
Date: Wed, 25 Jan 2023 09:26:40 +0530 [thread overview]
Message-ID: <20230125035640.yyppfo5zcdv6bqj2@vireshk-i7> (raw)
In-Reply-To: <20230124115323.21910-1-jonathanh@nvidia.com>
On 24-01-23, 11:53, Jon Hunter wrote:
> From: Yi-Wei Wang <yiweiw@nvidia.com>
>
> Populate the flag CPUFREQ_IS_COOLING_DEV for the Tegra194 CPUFREQ driver
> to register it as a cooling device. This enables CPU frequency
> throttling for CPUs when the passive trip points are crossed.
>
> Signed-off-by: Yi-Wei Wang <yiweiw@nvidia.com>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> drivers/cpufreq/tegra194-cpufreq.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/tegra194-cpufreq.c b/drivers/cpufreq/tegra194-cpufreq.c
> index 4596c3e323aa..5890e25d7f77 100644
> --- a/drivers/cpufreq/tegra194-cpufreq.c
> +++ b/drivers/cpufreq/tegra194-cpufreq.c
> @@ -411,7 +411,8 @@ static int tegra194_cpufreq_set_target(struct cpufreq_policy *policy,
>
> static struct cpufreq_driver tegra194_cpufreq_driver = {
> .name = "tegra194",
> - .flags = CPUFREQ_CONST_LOOPS | CPUFREQ_NEED_INITIAL_FREQ_CHECK,
> + .flags = CPUFREQ_CONST_LOOPS | CPUFREQ_NEED_INITIAL_FREQ_CHECK |
> + CPUFREQ_IS_COOLING_DEV,
> .verify = cpufreq_generic_frequency_table_verify,
> .target_index = tegra194_cpufreq_set_target,
> .get = tegra194_get_speed,
Applied. Thanks.
--
viresh
prev parent reply other threads:[~2023-01-25 3:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 11:53 [PATCH] cpufreq: tegra194: Enable CPUFREQ thermal cooling Jon Hunter
2023-01-25 3:56 ` Viresh Kumar [this message]
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=20230125035640.yyppfo5zcdv6bqj2@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=yiweiw@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