From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: [RFT][PATCH 0/2] ACPI / PM: Avoid spurious wakeups from non-wakeup GPEs in suspend-to-idle
Date: Tue, 18 Dec 2018 10:50:07 +0100 [thread overview]
Message-ID: <CAJZ5v0hCGoOB36sGDo1cfLN4tHbwmK+YGresjPAFPyXKUdbP=g@mail.gmail.com> (raw)
In-Reply-To: <20181217165025.GA2469@lahna.fi.intel.com>
On Mon, Dec 17, 2018 at 5:50 PM Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
>
> On Mon, Dec 17, 2018 at 12:19:27PM +0100, Rafael J. Wysocki wrote:
> > Hi All,
>
> Hi Rafael,
>
> > It turns out that on some systems non-wakeup GPEs cause trouble (see the
> > changelog of patch [1/2]), so they better should be disabled during
> > suspend-to-idle (at least before entering the main loop of it). This
> > is done in patch [1/2].
> >
> > Patch [2/2] is just a folllow-up.
>
> I tested both patches on Lenovo Carbon X1 6th generation and one new
> Dell system. Both default to s2idle. I did not see any issues around
> s2idle with the two patches applied.
>
> Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Thank you!
prev parent reply other threads:[~2018-12-18 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 11:19 [RFT][PATCH 0/2] ACPI / PM: Avoid spurious wakeups from non-wakeup GPEs in suspend-to-idle Rafael J. Wysocki
2018-12-17 11:21 ` [RFT][PATCH 1/2] ACPI: EC / PM: Disable non-wakeup GPEs for suspend-to-idle Rafael J. Wysocki
2018-12-17 11:22 ` [RFT][PATCH 2/2] ACPI: PM: Loop in full LPS0 mode only Rafael J. Wysocki
2018-12-17 16:50 ` [RFT][PATCH 0/2] ACPI / PM: Avoid spurious wakeups from non-wakeup GPEs in suspend-to-idle Mika Westerberg
2018-12-18 9:50 ` Rafael J. Wysocki [this message]
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='CAJZ5v0hCGoOB36sGDo1cfLN4tHbwmK+YGresjPAFPyXKUdbP=g@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@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).