From: Di Shen <di.shen@unisoc.com>
To: <rafael@kernel.org>, <daniel.lezcano@linaro.org>,
<amitk@kernel.org>, <rui.zhang@intel.com>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<xuewen.yan@unisoc.com>, <di.shen@unisoc.com>
Subject: [PATCH V2] thermal/of: Allow users to set governor for a thermal zone in DT
Date: Fri, 2 Dec 2022 17:11:11 +0800 [thread overview]
Message-ID: <20221202091111.1682-1-di.shen@unisoc.com> (raw)
In-Reply-To: <202212020239.CufwkKiR-lkp@intel.com>
The governor of all thermal zones can be initialized in
thermal_zone_device_register_with_trips(), but it is always the
def_governor, this means the governor of all thermal zones are
the same.
Allow users to set governor for a specific thermal zone in DT, in
this way, users can use different policies for thermal management.
Signed-off-by: Di Shen <di.shen@unisoc.com>
---
drivers/thermal/thermal_of.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/thermal/thermal_of.c b/drivers/thermal/thermal_of.c
index d4b6335ace15..4a29ac3be2ac 100644
--- a/drivers/thermal/thermal_of.c
+++ b/drivers/thermal/thermal_of.c
@@ -355,6 +355,7 @@ static struct thermal_zone_params *thermal_of_parameters_init(struct device_node
int coef[2];
int ncoef = ARRAY_SIZE(coef);
int prop, ret;
+ const char *governor_name;
tzp = kzalloc(sizeof(*tzp), GFP_KERNEL);
if (!tzp)
@@ -365,6 +366,11 @@ static struct thermal_zone_params *thermal_of_parameters_init(struct device_node
if (!of_property_read_u32(np, "sustainable-power", &prop))
tzp->sustainable_power = prop;
+ if (!of_property_read_string(np, "policy", &governor_name)) {
+ strncpy(tzp->governor_name, governor_name, THERMAL_NAME_LENGTH - 1);
+ tzp->governor_name[THERMAL_NAME_LENGTH - 1] = '\0';
+ }
+
/*
* For now, the thermal framework supports only one sensor per
* thermal zone. Thus, we are considering only the first two
--
2.17.1
next prev parent reply other threads:[~2022-12-02 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 8:54 [PATCH] " Di Shen
2022-12-01 18:42 ` kernel test robot
2022-12-02 9:11 ` Di Shen [this message]
2022-12-02 17:06 ` [PATCH V2] " Matthias Kaehlcke
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=20221202091111.1682-1-di.shen@unisoc.com \
--to=di.shen@unisoc.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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®