From: Lv Zheng <lv.zheng@intel.com>
To: "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <len.brown@intel.com>,
Robert Moore <robert.moore@intel.com>,
Lv Zheng <lv.zheng@intel.com>,
"David E . Box" <david.e.box@intel.com>
Cc: Lv Zheng <zetalog@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
devel@acpica.org
Subject: [PATCH 0/2] ACPICA: Events: Fix GPE enabling issues related to edge-triggered GPEs
Date: Fri, 11 Aug 2017 13:57:23 +0800 [thread overview]
Message-ID: <cover.1502430636.git.lv.zheng@intel.com> (raw)
There are 2 issues related to the enabling of GPEs:
1. Currently, our code clears GPE before enabling it. In case of edge
triggered GPEs, doing this risks GPE losses.
2. For edge-triggered GPEs, enabling it is not sufficiently to trigger an
already triggered GPE, we need to poll the GPE once it is enabled.
This patchset fixes these 2 problems.
Lv Zheng (2):
ACPICA: Events: Stop unconditionally clearing ACPI IRQs during
suspend/resume
ACPICA: Events: Dispatch GPEs after enabling for the first time
drivers/acpi/acpica/evgpe.c | 7 -------
drivers/acpi/acpica/evxfgpe.c | 22 ++++++++++++++++++++++
drivers/acpi/acpica/hwgpe.c | 1 -
drivers/acpi/acpica/hwsleep.c | 11 ++---------
drivers/acpi/acpica/hwxfsleep.c | 2 +-
5 files changed, 25 insertions(+), 18 deletions(-)
--
2.7.4
next reply other threads:[~2017-08-11 5:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 5:57 Lv Zheng [this message]
2017-08-11 5:57 ` [PATCH 1/2] ACPICA: Events: Stop unconditionally clearing ACPI IRQs during suspend/resume Lv Zheng
2017-08-11 5:57 ` [PATCH 2/2] ACPICA: Events: Dispatch GPEs after enabling for the first time Lv Zheng
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.1502430636.git.lv.zheng@intel.com \
--to=lv.zheng@intel.com \
--cc=david.e.box@intel.com \
--cc=devel@acpica.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox