From: Lukasz Luba <lukasz.luba@arm.com>
To: Xuewen Yan <xuewen.yan@unisoc.com>
Cc: linux-pm@vger.kernel.org, rafael@kernel.org, len.brown@intel.com,
linux-kernel@vger.kernel.org, ke.wang@unisoc.com,
xuewen.yan94@gmail.com, jeson.gao@unisoc.com, di.shen@unisoc.com,
pavel@ucw.cz
Subject: Re: [PATCH] power: energy_model: Rework the depends on for CONFIG_ENERGY_MODEL
Date: Thu, 19 Dec 2024 09:18:50 +0000 [thread overview]
Message-ID: <a43ebb14-be7f-4f8a-8892-cdb63eec4043@arm.com> (raw)
In-Reply-To: <20241219091109.10050-1-xuewen.yan@unisoc.com>
On 12/19/24 09:11, Xuewen Yan wrote:
> From: Jeson Gao <jeson.gao@unisoc.com>
>
> Now not only CPUs can use energy efficiency models, but GPUs
> can also use. On the other hand, even with only one CPU, we can also
> use energy_model to align control in thermal.
> So remove the dependence of SMP, and add the DEVFREQ.
That's true, there are 1-CPU platforms supported. Also, GPU can have
the EM alone.
>
> Signed-off-by: Jeson Gao <jeson.gao@unisoc.com>
> ---
> kernel/power/Kconfig | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/kernel/power/Kconfig b/kernel/power/Kconfig
> index afce8130d8b9..c532aee09e12 100644
> --- a/kernel/power/Kconfig
> +++ b/kernel/power/Kconfig
> @@ -361,8 +361,7 @@ config CPU_PM
>
> config ENERGY_MODEL
> bool "Energy Model for devices with DVFS (CPUs, GPUs, etc)"
> - depends on SMP
> - depends on CPU_FREQ
> + depends on CPU_FREQ || PM_DEVFREQ
> help
> Several subsystems (thermal and/or the task scheduler for example)
> can leverage information about the energy consumed by devices to
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
next prev parent reply other threads:[~2024-12-19 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 9:11 Xuewen Yan
2024-12-19 9:18 ` Lukasz Luba [this message]
2025-02-13 2:18 ` Xuewen Yan
2025-03-05 9:50 ` Lukasz Luba
2025-03-05 14:57 ` Rafael J. Wysocki
2025-03-05 15:14 ` Lukasz Luba
2025-03-06 19:38 ` Rafael J. Wysocki
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=a43ebb14-be7f-4f8a-8892-cdb63eec4043@arm.com \
--to=lukasz.luba@arm.com \
--cc=di.shen@unisoc.com \
--cc=jeson.gao@unisoc.com \
--cc=ke.wang@unisoc.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=xuewen.yan94@gmail.com \
--cc=xuewen.yan@unisoc.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®