From: Darren Hart <dvhart@infradead.org>
To: Mario.Limonciello@dell.com
Cc: jerome.debretagne@gmail.com, alex.hung@canonical.com,
platform-driver-x86@vger.kernel.org, andy@infradead.org,
rjw@rjwysocki.net, cwhuang@android-x86.org,
tristian.celestin@outlook.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: intel-hid: Missing power button release on some Dell models
Date: Sat, 12 Jan 2019 20:15:32 -0800 [thread overview]
Message-ID: <20190113041532.GB1349@wrath> (raw)
In-Reply-To: <057ab73bef634b4f8c474924eb6db572@ausx13mpc120.AMER.DELL.COM>
On Mon, Jan 07, 2019 at 03:36:48PM +0000, Mario.Limonciello@dell.com wrote:
>
>
> > -----Original Message-----
> > From: platform-driver-x86-owner@vger.kernel.org <platform-driver-x86-
> > owner@vger.kernel.org> On Behalf Of Jérôme de Bretagne
> > Sent: Sunday, January 6, 2019 11:57 AM
> > To: Alex Hung
> > Cc: platform-driver-x86@vger.kernel.org; Andy Shevchenko; Darren Hart;
> > Limonciello, Mario; Rafael J. Wysocki; Chih-Wei Huang; Tristian Celestin; linux-
> > kernel@vger.kernel.org
> > Subject: [PATCH] platform/x86: intel-hid: Missing power button release on some
> > Dell models
> >
> >
> > [EXTERNAL EMAIL]
> >
> > Power button suspend for some Dell models was added in:
> >
> > commit 821b85366284 (intel-hid: Power button suspend on Dell Latitude 7275)
I've addressed this one, but please do run checkpatch and correct reported
errors in the future. It checks commit reference format.
> >
> > by checking against the power button press notification (0xCE) to report
> > the power button press event. The corresponding power button release
> > notification (0xCF) was caught and ignored to stop it from being reported
> > as an "unknown event" in the logs.
> >
> > The missing button release event is creating issues on Android-x86, as
> > reported on the project mailing list for a Dell Latitude 5175 model, since
> > the events are expected in down/up pairs.
> >
> > Report the power button release event to fix this issue.
> >
> > Link: https://groups.google.com/forum/#!topic/android-x86/aSwZK9Nf9Ro
> > Tested-by: Tristian Celestin <tristian.celestin@outlook.com>
> > Tested-by: Jérôme de Bretagne <jerome.debretagne@gmail.com>
> > Signed-off-by: Jérôme de Bretagne <jerome.debretagne@gmail.com>
Queued for testing, thanks for the patch.
--
Darren Hart
VMware Open Source Technology Center
prev parent reply other threads:[~2019-01-13 4:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 17:56 Jérôme de Bretagne
2019-01-07 15:36 ` Mario.Limonciello
2019-01-13 4:15 ` Darren Hart [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=20190113041532.GB1349@wrath \
--to=dvhart@infradead.org \
--cc=Mario.Limonciello@dell.com \
--cc=alex.hung@canonical.com \
--cc=andy@infradead.org \
--cc=cwhuang@android-x86.org \
--cc=jerome.debretagne@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tristian.celestin@outlook.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
all inboxes | Powered by JetHome®