From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: daniel.lezcano@linaro.org, rui.zhang@intel.com, lukasz.luba@arm.com
Cc: sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: [PATCH] thermal/drivers/devfreq: Fix missing dependency with the energy model
Date: Tue, 15 Dec 2020 09:35:20 +0100 [thread overview]
Message-ID: <20201215083520.601988-1-daniel.lezcano@linaro.org> (raw)
In-Reply-To: <20201215125806.31495950@canb.auug.org.au>
The devfreq cooling device has been converted to use the energy model.
Add the dependency on the ENERGY_MODEL option to reflect this change
and prevent build failure if the option is not set.
Fixes: 615510fe13bd2 ("thermal: devfreq_cooling: remove old power model and use EM")
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
---
drivers/thermal/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/thermal/Kconfig b/drivers/thermal/Kconfig
index 7edc8dc6bbab..ee62d51ef351 100644
--- a/drivers/thermal/Kconfig
+++ b/drivers/thermal/Kconfig
@@ -193,6 +193,7 @@ config DEVFREQ_THERMAL
bool "Generic device cooling support"
depends on PM_DEVFREQ
depends on PM_OPP
+ depends on ENERGY_MODEL
help
This implements the generic devfreq cooling mechanism through
frequency reduction for devices using devfreq.
--
2.25.1
next prev parent reply other threads:[~2020-12-15 8:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 1:58 linux-next: build failure after merge of the thermal tree Stephen Rothwell
2020-12-15 8:35 ` Daniel Lezcano [this message]
2020-12-15 8:41 ` [PATCH] thermal/drivers/devfreq: Fix missing dependency with the energy model Daniel Lezcano
2020-12-15 8:48 ` Stephen Rothwell
2020-12-15 10:44 ` Lukasz Luba
2020-12-15 15:42 ` [PATCH] thermal: devfreq_cooling: fix the build when !ENERGY_MODEL Lukasz Luba
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=20201215083520.601988-1-daniel.lezcano@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rui.zhang@intel.com \
--cc=sfr@canb.auug.org.au \
/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