From: Lv Zheng <lv.zheng@intel.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>
Cc: Lv Zheng <lv.zheng@intel.com>, Lv Zheng <zetalog@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: [RFC PATCH 0/3] ACPI / PM: Move _PTS/_WAK invocations out of the noirq stage
Date: Tue, 28 Jun 2016 16:04:21 +0800 [thread overview]
Message-ID: <cover.1467100803.git.lv.zheng@intel.com> (raw)
Currently _PTS/_WAK are invoked during noirq stages, while in _PTS/_WAK,
there can be EC transactions. Though the EC driver is able to handle
transactions using polling mode, for the performance reason, it is better
to move _PTS/_WAK out of the noirq stage.
Lv Zheng (3):
PM: Rename prepare_late/wake suspend_ops callbacks to
prepare_noirq/finish_noirq
PM: Add prepare_late/finish_early suspend_ops callbacks
ACPI / PM: Fix EC polling issue by implementing
prepare_late/finish_early suspend_ops callbacks
arch/powerpc/platforms/pseries/suspend.c | 6 ++--
drivers/acpi/sleep.c | 9 +++---
include/linux/suspend.h | 50 +++++++++++++++++++++---------
kernel/power/suspend.c | 18 +++++++----
4 files changed, 55 insertions(+), 28 deletions(-)
--
1.7.10
WARNING: multiple messages have this Message-ID (diff)
From: Lv Zheng <lv.zheng@intel.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>
Cc: Lv Zheng <lv.zheng@intel.com>, Lv Zheng <zetalog@gmail.com>,
<linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: [RFC PATCH 0/3] ACPI / PM: Move _PTS/_WAK invocations out of the noirq stage
Date: Tue, 28 Jun 2016 16:04:21 +0800 [thread overview]
Message-ID: <cover.1467100803.git.lv.zheng@intel.com> (raw)
Currently _PTS/_WAK are invoked during noirq stages, while in _PTS/_WAK,
there can be EC transactions. Though the EC driver is able to handle
transactions using polling mode, for the performance reason, it is better
to move _PTS/_WAK out of the noirq stage.
Lv Zheng (3):
PM: Rename prepare_late/wake suspend_ops callbacks to
prepare_noirq/finish_noirq
PM: Add prepare_late/finish_early suspend_ops callbacks
ACPI / PM: Fix EC polling issue by implementing
prepare_late/finish_early suspend_ops callbacks
arch/powerpc/platforms/pseries/suspend.c | 6 ++--
drivers/acpi/sleep.c | 9 +++---
include/linux/suspend.h | 50 +++++++++++++++++++++---------
kernel/power/suspend.c | 18 +++++++----
4 files changed, 55 insertions(+), 28 deletions(-)
--
1.7.10
next reply other threads:[~2016-06-28 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 8:04 Lv Zheng [this message]
2016-06-28 8:04 ` [RFC PATCH 0/3] ACPI / PM: Move _PTS/_WAK invocations out of the noirq stage Lv Zheng
2016-06-28 8:04 ` [RFC PATCH 1/3] PM: Rename prepare_late/wake suspend_ops callbacks to prepare_noirq/finish_noirq Lv Zheng
2016-06-28 8:04 ` Lv Zheng
2016-06-28 8:04 ` [RFC PATCH 2/3] PM: Add prepare_late/finish_early suspend_ops callbacks Lv Zheng
2016-06-28 8:04 ` Lv Zheng
2016-06-28 8:04 ` [RFC PATCH 3/3] ACPI / PM: Fix EC polling issue by implementing " Lv Zheng
2016-06-28 8:04 ` Lv Zheng
2016-07-16 0:51 ` Rafael J. Wysocki
2016-07-19 4:40 ` Zheng, Lv
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=cover.1467100803.git.lv.zheng@intel.com \
--to=lv.zheng@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=zetalog@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.