From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <len.brown@intel.com>
Cc: ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>
Subject: [PATCH] thermal: Use freezable workqueue
Date: Tue, 8 Feb 2011 00:29:57 +0100 [thread overview]
Message-ID: <201102080029.57195.rjw@sisk.pl> (raw)
From: Rafael J. Wysocki <rjw@sisk.pl>
If thermal polling is enabled, which for example is the case for
ACPI thermal zones with the _TZP object defined, the thermal driver
uses delayed work items for this purpose. Unfortunately, since
they are queued up using schedule_delayed_work(), the work function
may be executed during system suspend or resume, which is not
desirable.
To prevent that from happening, use a freezable workqueue for
queuing up delayed work items in the thermal driver.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
---
drivers/thermal/thermal_sys.c | 22 ++++++++++++++++++++--
1 file changed, 20 insertions(+), 2 deletions(-)
Index: linux-2.6/drivers/thermal/thermal_sys.c
===================================================================
--- linux-2.6.orig/drivers/thermal/thermal_sys.c
+++ linux-2.6/drivers/thermal/thermal_sys.c
@@ -62,6 +62,20 @@ static DEFINE_MUTEX(thermal_list_lock);
static unsigned int thermal_event_seqnum;
+static struct workqueue_struct *thermal_wq;
+
+static int __init thermal_start_workqueue(void)
+{
+ thermal_wq = alloc_workqueue("thermal", WQ_FREEZEABLE, 0);
+ return thermal_wq ? 0 : -ENOMEM;
+}
+
+static inline void thermal_destroy_workqueue(void)
+{
+ if (thermal_wq)
+ destroy_workqueue(thermal_wq);
+}
+
static struct genl_family thermal_event_genl_family = {
.id = GENL_ID_GENERATE,
.name = THERMAL_GENL_FAMILY_NAME,
@@ -611,10 +625,10 @@ static void thermal_zone_device_set_poll
return;
if (delay > 1000)
- schedule_delayed_work(&(tz->poll_queue),
+ queue_delayed_work(thermal_wq, &(tz->poll_queue),
round_jiffies(msecs_to_jiffies(delay)));
else
- schedule_delayed_work(&(tz->poll_queue),
+ queue_delayed_work(thermal_wq, &(tz->poll_queue),
msecs_to_jiffies(delay));
}
@@ -1306,11 +1320,14 @@ static int __init thermal_init(void)
int result = 0;
result = class_register(&thermal_class);
+ if (!result)
+ result = thermal_start_workqueue();
if (result) {
idr_destroy(&thermal_tz_idr);
idr_destroy(&thermal_cdev_idr);
mutex_destroy(&thermal_idr_lock);
mutex_destroy(&thermal_list_lock);
+ thermal_destroy_workqueue();
}
result = genetlink_init();
return result;
@@ -1328,6 +1345,7 @@ static void __exit thermal_exit(void)
idr_destroy(&thermal_cdev_idr);
mutex_destroy(&thermal_idr_lock);
mutex_destroy(&thermal_list_lock);
+ thermal_destroy_workqueue();
genetlink_exit();
}
next reply other threads:[~2011-02-07 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 23:29 Rafael J. Wysocki [this message]
2011-02-08 4:47 ` [PATCH] thermal: Use freezable workqueue Dmitry Torokhov
2011-02-08 9:20 ` Rafael J. Wysocki
2011-02-08 9:32 ` Tejun Heo
2011-02-08 9:41 ` [PATCH wq#for-2.6.39] workqueue: add system_freezeable_wq Tejun Heo
2011-02-08 15:10 ` [linux-pm] " Alan Stern
2011-02-08 15:14 ` Tejun Heo
2011-02-08 15:32 ` Alan Stern
2011-02-08 17:58 ` Dmitry Torokhov
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=201102080029.57195.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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