From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
David Box <david.e.box@linux.intel.com>,
Chen Yu <yu.c.chen@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Tsuchiya Yuto <kitakar@gmail.com>,
Bob Moore <robert.moore@intel.com>,
Erik Kaneda <erik.kaneda@intel.com>
Subject: [PATCH 0/2] ACPI: PM: s2idle: Prevent spurious SCIs from waking up the system
Date: Tue, 11 Feb 2020 17:51:36 +0100 [thread overview]
Message-ID: <6974889.tv0o8xEHfr@kreacher> (raw)
Hi All,
On some systems the platform generates spurious SCIs while the system is
suspended to idle and those SCIs are treated as genuine system events after
the rework of the main suspend-to-idle control flow in 5.4. The patches
here address this problem by adding a mechanism to check whether or not
SCIs generated while the system is suspended to idle are spurious and to
discard the spurious ones.
Patch [1/2] updates ACPICA to provide a way to examine the status bits of
all GPEs enabled at the moment in one go.
Patch [2/2] uses that mechanism to implement the check mentioned above.
This series is on top of https://patchwork.kernel.org/patch/11373185/ which
should appear in linux-next tomorrow.
Thanks!
next reply other threads:[~2020-02-11 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 16:51 Rafael J. Wysocki [this message]
2020-02-11 16:52 ` [PATCH 1/2] ACPICA: Introduce acpi_any_gpe_status_set() Rafael J. Wysocki
2020-02-11 16:53 ` [PATCH 2/2] ACPI: PM: s2idle: Prevent spurious SCIs from waking up the system Rafael J. Wysocki
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=6974889.tv0o8xEHfr@kreacher \
--to=rjw@rjwysocki.net \
--cc=david.e.box@linux.intel.com \
--cc=erik.kaneda@intel.com \
--cc=kitakar@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=rui.zhang@intel.com \
--cc=yu.c.chen@intel.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).