From: Zoran Markovic <zoran.markovic@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: linux-pm@vger.kernel.org,
Shaibal Dutta <shaibal.dutta@broadcom.com>,
Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>,
Zoran Markovic <zoran.markovic@linaro.org>
Subject: [RFC PATCH] power: move pm_qos update timeout handler to power-efficient workqueue
Date: Fri, 31 Jan 2014 13:48:22 -0800 [thread overview]
Message-ID: <1391204902-13389-1-git-send-email-zoran.markovic@linaro.org> (raw)
From: Shaibal Dutta <shaibal.dutta@broadcom.com>
To avoid waking up idle CPUs, allow the scheduler to select the best CPU
to handle pm_qos update timeouts. This extends idle residency times and
conserves power.
This functionality is enabled when CONFIG_WQ_POWER_EFFICIENT is selected.
Cc: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Len Brown <len.brown@intel.com>
Signed-off-by: Shaibal Dutta <shaibal.dutta@broadcom.com>
[zoran.markovic@linaro.org: Rebased to latest kernel. Fixed code alignment.
Added commit message.]
Signed-off-by: Zoran Markovic <zoran.markovic@linaro.org>
---
kernel/power/qos.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/power/qos.c b/kernel/power/qos.c
index 8dff9b4..5e35a3a 100644
--- a/kernel/power/qos.c
+++ b/kernel/power/qos.c
@@ -405,7 +405,8 @@ void pm_qos_update_request_timeout(struct pm_qos_request *req, s32 new_value,
pm_qos_array[req->pm_qos_class]->constraints,
&req->node, PM_QOS_UPDATE_REQ, new_value);
- schedule_delayed_work(&req->work, usecs_to_jiffies(timeout_us));
+ queue_delayed_work(system_power_efficient_wq,
+ &req->work, usecs_to_jiffies(timeout_us));
}
/**
--
1.7.9.5
reply other threads:[~2014-01-31 21:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1391204902-13389-1-git-send-email-zoran.markovic@linaro.org \
--to=zoran.markovic@linaro.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=shaibal.dutta@broadcom.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;
as well as URLs for NNTP newsgroup(s).