From: Darren Hart <dvhart@infradead.org>
To: Mario Limonciello <mario.limonciello@dell.com>
Cc: AceLan Kao <acelan.kao@canonical.com>,
linux-pm@vger.kernel.org,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org, Len Brown <lenb@kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH] intel-vbtn: match power button on press rather than release
Date: Fri, 4 Aug 2017 10:29:53 -0700 [thread overview]
Message-ID: <20170804172953.GC21169@fury> (raw)
In-Reply-To: <1501866006-24811-1-git-send-email-mario.limonciello@dell.com>
On Fri, Aug 04, 2017 at 12:00:06PM -0500, Mario Limonciello wrote:
> This fixes a problem where the system gets stuck in a loop
> unable to wakeup via power button in s2idle.
>
> The problem happens because:
> - press power button:
> - system emits 0xc0 (power press), event ignored
> - system emits 0xc1 (power release), event processed,
> emited as KEY_POWER
> - set wakeup_mode to true
> - system goes to s2idle
> - press power button
> - system emits 0xc0 (power press), wakeup_mode is true,
> system wakes
> - system emits 0xc1 (power release), event processed,
> emited as KEY_POWER
> - system goes to s2idle again
>
> To avoid this situation, process the presses (which matches what
> intel-hid does too).
>
> Verified on an Dell XPS 9365
>
> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
This looks good to me - responding to the release is non-intuitive IMHO
anyway. I'd like to see agreement from AceLan, but this should go into
the 4.13 rc cycle (at rc3 currently).
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2017-08-04 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 17:00 [PATCH] intel-vbtn: match power button on press rather than release Mario Limonciello
2017-08-04 17:29 ` Darren Hart [this message]
2017-08-04 23:30 ` Rafael J. Wysocki
2017-08-05 20:57 ` Darren Hart
2017-08-05 22:20 ` Rafael J. Wysocki
2017-08-06 23:24 ` Darren Hart
2017-08-07 0:38 ` Rafael J. Wysocki
2017-08-07 0:59 ` AceLan Kao
2017-08-07 3:54 ` Darren Hart
2017-09-16 13:45 ` Pali Rohár
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=20170804172953.GC21169@fury \
--to=dvhart@infradead.org \
--cc=acelan.kao@canonical.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.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).