From: Chen Yu <yu.c.chen@intel.com>
To: linux-pm@vger.kernel.org, edubezval@gmail.com, javi.merino@arm.com
Cc: rui.zhang@intel.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: [PATCH 3/3] Thermal: do thermal zone update after a cooling device registered
Date: Sun, 27 Sep 2015 13:48:44 +0800 [thread overview]
Message-ID: <1443332924-14028-1-git-send-email-yu.c.chen@intel.com> (raw)
From: Zhang Rui <rui.zhang@intel.com>
When a new cooling device is registered, we need to update the
thermal zone to set the new registered cooling device to a proper
state.
This fixes a problem that the system is cool, while the fan devices
are left running on full speed after boot, if fan device is registered
after thermal zone device.
CC: <stable@vger.kernel.org> #3.18+
Reference:https://bugzilla.kernel.org/show_bug.cgi?id=92431
Tested-by: Manuel Krause <manuelkrause@netscape.net>
Tested-by: szegad <szegadlo@poczta.onet.pl>
Tested-by: prash <prash.n.rao@gmail.com>
Tested-by: amish <ammdispose-arch@yahoo.com>
Signed-off-by: Zhang Rui <rui.zhang@intel.com>
Signed-off-by: Chen Yu <yu.c.chen@intel.com>
---
drivers/thermal/thermal_core.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
index c3bdb48..09c78a4 100644
--- a/drivers/thermal/thermal_core.c
+++ b/drivers/thermal/thermal_core.c
@@ -1450,6 +1450,7 @@ __thermal_cooling_device_register(struct device_node *np,
const struct thermal_cooling_device_ops *ops)
{
struct thermal_cooling_device *cdev;
+ struct thermal_instance *pos, *next;
int result;
if (type && strlen(type) >= THERMAL_NAME_LENGTH)
@@ -1494,6 +1495,15 @@ __thermal_cooling_device_register(struct device_node *np,
/* Update binding information for 'this' new cdev */
bind_cdev(cdev);
+ list_for_each_entry_safe(pos, next, &cdev->thermal_instances, cdev_node) {
+ if (next->cdev_node.next == &cdev->thermal_instances) {
+ thermal_zone_device_update(next->tz);
+ break;
+ }
+ if (pos->tz != next->tz)
+ thermal_zone_device_update(pos->tz);
+ }
+
return cdev;
}
--
1.8.4.2
next reply other threads:[~2015-09-27 5:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 5:48 Chen Yu [this message]
2015-09-28 14:29 ` [PATCH 3/3] Thermal: do thermal zone update after a cooling device registered Javi Merino
2015-09-28 17:52 ` Chen, Yu C
2015-09-29 16:01 ` Javi Merino
2015-10-12 9:23 ` Chen, Yu C
2015-10-14 17:07 ` Javi Merino
2015-10-14 19:21 ` Chen, Yu C
2015-10-14 19:23 ` Chen, Yu C
2015-10-15 14:05 ` Javi Merino
2015-10-20 1:05 ` Chen, Yu C
2015-10-20 1:44 ` Chen, Yu C
2015-10-20 9:47 ` Javi Merino
-- strict thread matches above, loose matches on Subject: below --
2015-03-24 5:21 [PATCH 0/3] Thermal: thermal enhancements for boot and system sleep Zhang Rui
2015-03-24 5:21 ` [PATCH 3/3] Thermal: do thermal zone update after a cooling device registered Zhang Rui
2015-03-24 15:12 ` Eduardo Valentin
2015-03-25 2:27 ` Zhang, Rui
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=1443332924-14028-1-git-send-email-yu.c.chen@intel.com \
--to=yu.c.chen@intel.com \
--cc=edubezval@gmail.com \
--cc=javi.merino@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).