From: "Clément Péron" <peron.clem@gmail.com>
To: Rob Herring <robh@kernel.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Steven Price <steven.price@arm.com>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Clément Péron" <peron.clem@gmail.com>
Subject: [PATCH v4 11/14] arm64: defconfig: Enable devfreq cooling device
Date: Fri, 10 Jul 2020 11:25:45 +0200 [thread overview]
Message-ID: <20200710092548.316054-12-peron.clem@gmail.com> (raw)
In-Reply-To: <20200710092548.316054-1-peron.clem@gmail.com>
Devfreq cooling device framework is used in Panfrost
to throttle GPU in order to regulate its temperature.
Enable this driver for ARM64 SoC.
Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
Signed-off-by: Clément Péron <peron.clem@gmail.com>
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 89538d9e39e5..8a295bcb4dd3 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -504,6 +504,7 @@ CONFIG_SENSORS_INA2XX=m
CONFIG_SENSORS_INA3221=m
CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y
CONFIG_CPU_THERMAL=y
+CONFIG_DEVFREQ_THERMAL=y
CONFIG_THERMAL_EMULATION=y
CONFIG_QORIQ_THERMAL=m
CONFIG_SUN8I_THERMAL=y
--
2.25.1
next prev parent reply other threads:[~2020-07-10 9:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 9:25 [PATCH v4 00/14] Add regulator devfreq support to Panfrost Clément Péron
2020-07-10 9:25 ` [PATCH v4 01/14] drm/panfrost: avoid static declaration Clément Péron
2020-07-10 9:25 ` [PATCH v4 02/14] drm/panfrost: clean headers in devfreq Clément Péron
2020-07-10 9:25 ` [PATCH v4 03/14] drm/panfrost: don't use pfdevfreq.busy_count to know if hw is idle Clément Péron
2020-07-10 9:25 ` [PATCH v4 04/14] drm/panfrost: introduce panfrost_devfreq struct Clément Péron
2020-07-10 9:46 ` Clément Péron
2020-07-10 9:25 ` [PATCH v4 05/14] drm/panfrost: use spinlock instead of atomic Clément Péron
2020-07-10 9:25 ` [PATCH v4 06/14] drm/panfrost: properly handle error in probe Clément Péron
2020-07-10 9:25 ` [PATCH v4 07/14] drm/panfrost: rename error labels in device_init Clément Péron
2020-07-10 9:25 ` [PATCH v4 08/14] drm/panfrost: move devfreq_init()/fini() in device Clément Péron
2020-07-10 9:25 ` [PATCH v4 09/14] drm/panfrost: dynamically alloc regulators Clément Péron
2020-07-10 9:25 ` [PATCH v4 10/14] drm/panfrost: add regulators to devfreq Clément Péron
2020-07-10 9:25 ` Clément Péron [this message]
2020-07-10 9:25 ` [PATCH v4 12/14] arm64: dts: allwinner: h6: Add cooling map for GPU Clément Péron
2020-07-10 9:25 ` [PATCH v4 13/14] [DO NOT MERGE] arm64: dts: allwinner: h6: Add GPU OPP table Clément Péron
2020-07-10 9:25 ` [PATCH v4 14/14] [DO NOT MERGE] arm64: dts: allwinner: force GPU regulator to be always Clément Péron
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=20200710092548.316054-12-peron.clem@gmail.com \
--to=peron.clem@gmail.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.com \
--cc=vireshk@kernel.org \
--cc=wens@csie.org \
/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